Project automation didn't run for an earlier event
Updated
Applies to: Super Admins, Creators, and Integrators
A project automation reacts only to events that happen while it's on the project. If the event came first, the project's Logs has no row for it, and the automation won't run for it later. Here's how to check, and what you can do now.
Why it happens
An automation starts watching for its trigger once it's on the project. Nothing runs for earlier events, and the app has no way to re-run an automation for a past event.
The When a task is overdue trigger is the exception. It's checked on a schedule rather than at the moment of an event. An automation with this trigger also runs for tasks that are already open and overdue by its number of days, even when they went overdue before it was added. This trigger is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.
Each automation on a project is a copy, made when it was added:
From the playbook, when the project is created from it.
From the Library, when it's imported into the project or comes with a library module. Later edits to the automation in the Library don't change existing copies unless someone with permission selects Push update… on the Library automation to send the new version to them.
Built on the project with Create. Its
Createrow in Logs shows when it was added.
Later changes to a playbook's automations don't reach existing projects on their own. When playbook updates are turned on for your organization, publishing a new playbook or library module version can push new, changed or deleted automations into active projects. The review shows Won’t run — its trigger already happened for a pushed automation with a one-time trigger that already happened in a project. That's always the case for When project created, and for When module completed or When task completed when that module or task is already complete. Other triggers never get this tag.
Watch for two cases:
A playbook added to a project after the project was created, for example from Choose from Library on a new project's welcome screen, copies its automations onto the project along with its modules and tasks. The project also takes on the playbook's project settings, and its project data field values are reset. A playbook added through the API brings only its modules and tasks, not its automations. Either way, the copied automations react only to events that happen after they're added. The exception is a copied When a task is overdue automation, which also runs for tasks that are already open and overdue by its number of days.
A When project created automation runs only when a project is created. One added to an existing project never runs. If you try to import one from the Library into an active project, you see the error
'When project created' automations can't be added to an active project — they only run at creation time.
Fix it
Open the project from Projects.
Select the Automations tab.
Look for the automation in the list. If it isn't there, it was never copied to this project or has since been deleted.
To add it to this project, select Create.
Select the trigger, then add each action with Add Action.
Select Create to save the automation.
For the event that already happened, make the automation's change by hand, for example in Salesforce or HubSpot. Or repeat the event, if that's possible for its trigger.
After the next event, select Logs.
Select Refresh to see the new row.
Instead of steps 4 to 6, you can select Import from library to add an automation from the Automations Library.
Warning: Repeating an event runs every automation it triggers, not only this one.
To give future projects the automation, add it on the playbook's Automations tab too.
If several active projects are missing the automation, you don't have to rebuild it on each one:
If you're a Super Admin or Creator and playbook updates are turned on, publish the playbook change and choose to update active projects now. Integrators can't push playbook updates. Playbook and Library Overview covers publishing.
From the Automations Library, use the automation's Apply to… action to add it to many projects at once. See Automations Library: build an automation once, reuse it everywhere.
Either way, the automation runs only for events that happen after it's added.
Still stuck?
Contact support with the project's name and link, the automation's trigger and actions, where it came from (the playbook, the Library, or built on the project), and when the event happened.