When a SuiteDash automation stops working, the instinct is to rebuild it. Usually you don’t need to. Most problems come from something the automation depends on, and you can find it by checking a few things in order.
1. Is the trigger still the event you expect?
Most broken automations are waiting for an event that no longer happens the way they expect. A form was replaced with a new one, a pipeline stage was renamed, or a tag was retired. The automation still points at the old version.
Open the automation and confirm its trigger points at the form, stage, tag or date you use today.
2. Do the conditions exclude your test contact?
Conditions narrow who an automation applies to. If you test with a contact that doesn’t match, nothing happens, and it looks broken.
Check each condition against the record you are testing with, or test with a contact that matches every condition.
3. Does another automation change the same record first?
When two automations act on the same record, the result depends on which runs first. One might change a status or tag before the other can react to it.
List every automation that uses the same trigger or touches the same records. Merge or remove the ones that overlap.
4. Is the template it uses still active?
Automations that send emails, create projects or apply templates fail quietly when the template has been deleted or changed.
Open each template the automation uses and confirm it still exists and looks right.
5. Is it on the right plan?
The complete automation toolkit and FLOWs are part of SuiteDash’s Pinnacle plan. If your account changed plans, some automation features may no longer be available.
Prevent it next time
Keep a simple list of every automation: what triggers it, what it does and who owns it. When you change a form, stage or tag, check the list first. It turns a day of detective work into a five-minute check.
If you would rather hand it over, our SuiteDash support team fixes automations and tests them with a real client journey before handing back.
Questions
Why is my SuiteDash automation firing twice?
Usually because two automations react to the same event, or one automation changes a record in a way that triggers another. List every automation that uses the same trigger, merge the ones that overlap, and check whether any automation updates a tag or status that another one is watching.