Project automation didn't run: the event doesn't match the trigger
Updated
Applies to: Super Admins, Creators, and Integrators
This article covers one cause of a project automation not running: its trigger waits for a different event than the one that happened. We'll take this one step at a time.
Why it happens
Each trigger starts on one kind of event, and similar events don't count. Find your trigger in this table.
Trigger | Runs when | Doesn't run when |
|---|---|---|
Task completed, Any task completed | A task is completed. Task completed waits for the task chosen in Task. If Task completed has Only trigger when a specific subtask answer matches checked, the chosen subtask's answer must also match the Expected answer. | A task is edited or re-opened, a subtask is answered while the task stays open, or, for Task completed, the subtask answer doesn't match the Expected answer |
Subtask completed | The subtask chosen in Subtask is completed. If an Expected answer is set, the answer must also match it. | A different subtask is completed, only the task is, or the answer doesn't match the Expected answer |
Project created | Right after the project is created. If the playbook sets a data field condition, it runs only when that project data field equals the value when the project is created. | The automation is added after the project exists, the data field doesn't equal the value at creation, or the condition's data field is no longer available |
Project owner or status changed | The owner or status changes, if its box is checked: Owner changes or Status changes | Any other project detail changes |
Project completion % reached | Completion rises to the Completion threshold (%) or past it | Completion was already at or past the threshold, or it goes down |
Specific Project datafield changed, Any Project datafield changed | A project data field changes to a new value. If Specific Project datafield changed sets Only trigger when the value matches (optional), the new value must match it. | A task or account data field changes, or the new value doesn't match the value set in the trigger. Any Project datafield changed also doesn't run when a formula data field's value changes on its own, without anyone editing the project. |
Module completed | The module chosen in Module is completed | A different module is completed |
Module added | Any module is added to the project | — |
Internal note made | An internal note is made on the project | — |
The Automations tab also offers Project updated and Project completed, which this table doesn't cover.
Three more details can matter:
In a playbook, a Project created trigger can be limited with Only trigger when data field (optional) and equals. The condition is checked once, when the project is created. If the data field is no longer available, the editor shows a warning and offers Remove condition. On the project's Automations tab, the condition is read-only and reads "Only triggered when <field> equals <value>".
Project completion % reached counts only tasks shown on the customer portal. Tasks whose Visibility is Not on Portal are left out, so this percentage can differ from the progress shown elsewhere in the app.
A project made with a workflow's Debug button and Run and Create Records skips its Project created automations.
Fix it
Open the project from Projects.
Select the Automations tab.
Select the automation in the list. Its trigger is the first step under Workflow.
Compare the trigger with the event, using the table in Why it happens.
If a trigger setting is off, select the trigger and correct it, for example the Task or the Completion threshold (%).
Select Save.
Repeat the event on the project. To test Project created, add the automation to the playbook, then create a new project from it.
Select Logs.
Select Refresh to load the new row.
A trigger can't be swapped while its automation has actions. To use a different trigger, build a new automation with Create, then remove the old one with Delete Rule.
Warning: Repeating an event runs every automation it triggers, not only this one.
Still stuck?
Contact support with the project's name and link, the automation's trigger and its settings, and what happened on the project, with the date and time.