Why Didn't My Automation Run?

Why Didn't My Automation Run?

Sometimes you set up an automation and expect it to fire, but nothing happens. Here are the most common reasons and how to fix them.

The automation is not activeAn automation only runs when it is turned on. If you saved it but did not activate it, or if it was turned off at some point, it will not fire.

 
Fix: Check the automation list and make sure the toggle is set to active.
The trigger does not match the eventThe most common issue. Your automation listens for a specific event, but the thing that happened does not match what the trigger expects.
 
For example:

• You set the trigger to Contact Form Submitted, but the submission came through a brochure form (which uses Brochure Submitted)
• You set the trigger to Invoice Paid in Full, but it was a deposit with a remaining balance (use First Payment Made instead)
• You set the trigger to File Completed, but the document was a brochure or contact form (those types don't fire File Completed)
• You used Client Signed Contract but the document wasn't a contract type

 
Fix: Check that the trigger type matches exactly what happened. Review the trigger descriptions to make sure the event qualifies.
A trigger filter is excluding the eventIf you set filters on the trigger (like "only fire for this specific form" or "only fire for this package"), the automation quietly skips events that do not match. It will not show an error. It just does not run.
 
Fix: Review any trigger-level filters and confirm the event matches those filters.
The automation already ran for this eventTalleFlow prevents the same automation from running multiple times for the exact same event. This deduplication protects you from accidental double-sends or duplicate tasks.
 
Fix: If you expect the automation to run again, confirm this is actually a new event and not the same one being processed twice.
The event happened before the automation was createdAutomations only fire for events that happen after the automation is set up and activated. They do not retroactively process past events.
 
Fix: If you need to trigger the workflow for something that already happened, you may need to re-trigger the event (like re-submitting the form or re-creating the project).
A condition is blocking the next stepsIf the automation started but a specific action did not happen, a condition node may be blocking it. The automation ran, but a rule checked mid-workflow prevented the next step from continuing.
 
Fix: Check the condition node in your workflow. Make sure the data matches what the condition expects.
You added a condition to a time-based triggerConditions are not supported for scheduled triggers (Time Based, Project Date, Meeting Starts, Meeting Ends). The condition will always be skipped at runtime.
 
Fix: Remove the condition node, or switch to an event-based trigger.
Common confusion: Invoice Paid in Full vs. First Payment MadeInvoice Paid in Full only fires when an invoice is completely paid. If a client makes a deposit but there is still a remaining balance, it will NOT fire. Use First Payment Made if you want to react to the initial payment regardless of balance.
Common confusion: File Completed vs. Client Signed ContractBoth can fire for the same contract being signed. If you have automations on both, you may get duplicate actions. Pick one or add conditions to prevent overlap.
 
File Completed is broader (covers contracts, questionnaires, proposals, invoices). Client Signed Contract only fires for contracts specifically.
Still stuck?If none of the above applies, reach out to support with:

• The name of the automation
• What event you expected to trigger it
• When the event happened

 
This helps us find exactly where the workflow stopped.