Restoring missed handoffs risks writing the same customer work twice.
Project continuity depends on recovering missed events, while Work Graph history must remain trustworthy.
Who you’d be doing this for
“I can see the request in the project, but the approver never got a task and now everyone is asking me where it went.”
Alok Choudhury · Enterprise Project Manager
Runs approval workflows that create work through the public API and depend on Automations to assign the next owner.
What is at stake
Approval tasks are missing after API-created work enters projects, even though the tasks are visible. You must weigh fast recovery against irreversible duplicate actions in customer workflows.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- approval continuity vs. duplicate customer actions
- historical recovery vs. ownership validity
- fast containment vs. complete restoration
- inferred event history vs. auditable evidence
Why Asana
Public API workflows and Automations carry enterprise work across the Work Graph.
Written with these in mind
Not your kind of problem? 28 more at Asana, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.