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

Updated

Applies to: Super Admins, Creators, and Integrators

Super Admins, Creators and Integrators see the Automations tab on a project. Contributors and Collaborators don't.

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 Task completed, the Subtask and Expected answer fields only appear when Only trigger when a specific subtask answer matches is selected.

On Subtask completed, the Expected answer field only appears when Only trigger when the subtask answer matches a specific value is selected. That checkbox only appears when the selected subtask is a type that can be matched on its answer.

For other subtask types, the trigger runs whenever the subtask is completed. On Specific Project datafield changed, it's the value in Only trigger when the value matches (optional).

For dropdown, multi-select, date, number, monetary and user data fields, you choose that value with the field's own picker instead of typing it. If you leave it empty, the trigger runs on any change.

On Project created, a playbook's automation can be limited with Only trigger when data field (optional) and equals.

That value is checked once, when the project is created. 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.

  • For a checkbox field inside a form subtask, the answer matches when the expected value is one of the options chosen.

  • For a multi-select data field, the expected value is a set of options. It matches only when every expected option is among those chosen. Other chosen options don't stop it from matching.

  • A standalone multiple-selection subtask can't be matched on one option. On Subtask completed, the checkbox doesn't appear, so the trigger runs whenever the subtask is completed. On Task completed, its answer is compared as a single text value, so it won't match a single option.

  • For a user data field, you pick the person in the condition. It matches when the field holds that person. Older conditions saved as a full name still match on the 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 and select the Automations tab.

  2. Select the automation, then select its trigger, the first step under Workflow.

  3. For Task completed, check that Only trigger when a specific subtask answer matches is selected. For Subtask completed, check that Only trigger when the subtask answer matches a specific value is selected. The expected answer only shows when it is. For Project created, the trigger only shows its condition, as Only triggered when the field equals the value. You can't edit it on the project.

  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. For Yes/No and dropdown subtasks, choose it from the Expected answer list. For dropdown, multi-select, date, number, monetary and user data fields, set it in Only trigger when the value matches (optional) with the field's own picker. If Subtask is empty, select the subtask again.

  6. Select Save.

  7. If the project came from a playbook, correct the expected value in the playbook's Automations tab too. A project's automations are copied from its playbook when the project is created, so new projects would repeat the mismatch. See Understanding Playbook & Project Automations.

  8. To run the automation for this task, open the task. If it's complete, select Re-Open Task, then Continue.

  9. For Subtask completed, answer the subtask again. For Task completed, check the answer, then select Complete Task. On a customer task, select Mark Task Complete, then Continue.

  10. Select Logs, then select Refresh to load the new row.

A Specific Project datafield changed trigger runs the next time the field changes to the expected value. A Project created trigger is checked once, when the project is created, so changing the field later doesn't run it. New projects created from the corrected playbook pick up the fix.

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.

More in Getting Unstuck Fast