Project automation didn't run: the answer or value didn't match

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 trigger checks a subtask answer or a data field value, a mismatch stops it before any action runs. The event happened, but the project's Logs has no row for it. We'll find the mismatch one step at a time.

Why it happens

A trigger can wait for one value. On Task completed and Subtask completed, it's the Expected answer. On Specific Project datafield changed, it's the value in Only trigger when the value matches (optional). The automation runs only when the saved answer or value matches it exactly:

  • Capitals count: Enterprise doesn't match enterprise. Spaces before or after the text are ignored.
  • A checkbox or multi-select answer matches when the expected value is one of the options chosen.
  • A user data field matches the person's first and last name.
  • An unanswered subtask never matches. That includes a subtask that conditional logic skipped.
  • Task completed checks the answer once, when the task is completed. If the subtask had no answer then, it didn't match. Answers lock when a task is completed, so a later answer can't run it.

Fix it

  1. Open the project from Projects.
  2. Select the Automations tab.
  3. Select the automation, then select its trigger, the first step under Workflow.
  4. Compare the expected value with the real one. For a subtask, open the task and read the answer. For a data field, check the project's Data Fields tab.
  5. If the expected value is wrong, correct it. If Subtask is empty, select the subtask again.
  6. Select Save.
  7. To run the automation for this task, open the task. If it's complete, select Re-Open Task, then Continue.
  8. For Subtask completed, answer the subtask again. For Task completed, check the answer, then select Complete Task, or Mark Task Complete on a customer task.
  9. Select Logs.
  10. Select Refresh to load the new row.

A data field trigger runs the next time the field changes to the expected value.

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 task and subtask or the data field, the trigger's expected value, the answer that was saved, and when the task was completed.

Related articles