Action Runs need a visible failure state without changing successful workflow behavior.
Partner developers need an immediate answer while existing API consumers need stable responses.
Who you’d be doing this for
“I got paged for duplicate runs again, and the API still makes both attempts look unfinished.”
Eero Lindberg · Platform Engineer
Builds the embedded workflow screen for a software company using the Workflow API.
What is at stake
Failed runs are being submitted again because embedded screens cannot tell failure from processing. You have to weigh a clearer status signal against compatibility for existing API consumers.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- failure clarity vs API compatibility
- faster retries vs duplicate execution
- embedded experience needs vs execution stability
- flagged learning vs broad release
Why Zapier
Powered by Zapier API partners depend on embedded workflow visibility to support automation inside their own products.
Written with these in mind
Not your kind of problem? 3 more at Zapier, 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.