Project automation didn't run for an earlier event

Last updated: October 2, 2026

Applies to: Super Admins, Creators, and Integrators

Project automations are available when they're turned on for your organization. If you don't see an Automations tab on your projects, contact your OnRamp team.

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.

Each automation on a project is a copy, made when it was added:

  • From the playbook, when the project is created from it. Automations added to the playbook later don't reach existing projects, and edits to the playbook's automations don't change them.
  • From the Library, when it's imported into the project or comes with a library module. Later edits in the Library don't change the copy.
  • Built on the project with Create. Its Create row in Logs shows when it was added.

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, brings its modules and tasks but not its automations.
  • A Project created automation runs only when a project is created. One added to an existing project never runs.

Fix it

  1. Open the project from Projects.
  2. Select the Automations tab.
  3. Look for the automation in the list. If it isn't there, it was never copied to this project.
  4. To add it to this project, select Create.
  5. Select the trigger, then add each action with Add Action.
  6. Select Create to save the automation.
  7. For the event that already happened, make the automation's change by hand, for example in Salesforce or HubSpot. Or repeat the event, if its trigger allows it.
  8. After the next event, select Logs.
  9. Select Refresh to see the new row.

If your organization has the Automations Library, you can select Import from library instead of steps 4 to 6. To give future projects the automation, add it on the playbook's Automations tab too.

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 actions, where it came from (the playbook, the Library, or built on the project), and when the event happened.

Related articles