Project automation didn't run after another automation's change

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.

When a project automation changes something in OnRamp, that change never starts another project automation. This guard keeps automations from setting each other off in a loop. We'll show you how to get the result you wanted another way.

Why it happens

Three actions change the project itself: Update a data field, Change task data, and, where it's turned on for your organization, Add a module. A change from one of these actions doesn't start other automations. For example:

  • Update a data field doesn't start Specific Project datafield changed or Any Project datafield changed automations.
  • Add a module doesn't start Module added automations.

In Logs, you'll see the first automation's row, such as Update Data Field or Add Module, with a check mark in Success. There's no row for the automation you expected next. The same change made by a person still starts automations as usual.

This applies to every automation on the project, including ones copied from a playbook or the Library.

Fix it

Give the first automation the other automation's actions, so one trigger does both jobs. Some actions don't run on every trigger, though. Add a module doesn't run on Module added or Any task completed. Update a data field doesn't run on Specific Project datafield changed or Any Project datafield changed.

  1. Open the project from Projects.
  2. Select the Automations tab.
  3. Select the automation that makes the change.
  4. Select Add Action, then select the action the other automation runs. New actions go at the end, so it runs after the change.
  5. Set up the action the same way as in the other automation.
  6. Select Save.
  7. Repeat the event that starts this automation. This runs every automation that event triggers.
  8. Select Logs.
  9. Select Refresh. Each action that ran has its own row.

If these automations came from the playbook, make the same change on the playbook's Automations tab, so new projects get it too.

Still stuck?

Contact support with the project's name and link, the trigger and actions of both automations, and the Timestamp of the first automation's row.

Related articles