Change task data automation failed
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 Change task data action changes tasks in the project each time its automation runs. It can set their due and start dates, type, visibility, assignee, and assignee restrictions. If the tasks didn't change, the project's log shows what stopped it. We'll go through each cause and its fix.
Why it happens
When the change fails, the log row's Action shows Change Task Data, Success shows an X, and the tasks stay as they were. To read the reason, select View in the row's Error column, and find the message line. To find the row, see Project automation didn't run or failed.
Some causes apply only to a copied automation, one that came into the project from a playbook, a Library module, or the Automations Library.
| What you see in Logs | Cause |
|---|---|
Error includes No task fields specified to change |
Every field the action can change is blank or set to Leave unchanged, so there's nothing to change. |
Error includes Task ID is required for Change Task Data action |
No tasks are chosen in Tasks to change. |
Error includes not found in project |
A task chosen in Tasks to change is no longer in this project, for example because it was deleted. |
Error includes A source task is required for a relative Change Task Data action |
A copied automation is set to change specific tasks, but none were chosen. |
Error includes did not fire from a task |
A copied automation is set to Change the task that triggered this automation, but its trigger isn't Task completed, Any task completed, or Subtask completed. |
Error includes Invalid assignee ID or Invalid assignee restriction IDs |
Someone chosen in Assignee or Assignee restrictions isn't a member of this project. |
Error includes Unable to determine user to attribute the task change |
OnRamp records who made the change: the person whose action triggered the automation, or else the project owner or the project's creator. It found none of them. |
No Change Task Data row, on a copied automation |
It's set to change specific tasks, and this project has no copy of any of them. OnRamp skips the action without a row. |
If you see any other message, or Action shows changeTaskData, something unexpected stopped the action. Contact support with the details in Still stuck?.
Fix it
- Open the project from Projects, and select the Automations tab.
- In the list of automations, select the one with the Change task data step, and then select that step.
- Make the change for your row:
No task fields specified to change: Check that Tasks to change lists tasks. Then set at least one field, such as Task type or Assignee.Task ID is required for Change Task Data action,not found in project,A source task is required for a relative Change Task Data action,did not fire from a task, or no row: In Tasks to change, select the tasks to change. The action then changes these tasks each time it runs.Invalid assignee IDorInvalid assignee restriction IDs: In Assignee and Assignee restrictions, select current members of this project.Unable to determine user to attribute the task change: Select the project's Settings tab, and select a Project Owner.
- If you changed the automation, select Save.
- To check the fix, repeat the event on the project. Some triggers, such as Project created, happen only once per project.
- Select Logs, and then select Refresh to load the new row.
Still stuck?
Contact support with the project's name and link, the automation's trigger, the names of the tasks it should change, the row's Timestamp, and the text from Error and Payload.