Restart one workflow execution
POST /workflows/executions/{execution_id}/restart
Runs the workflow again FROM THE BEGINNING. Not a resume.
Nodes that already succeeded run a second time. If any of them sent an
email, posted to Slack or called a paid API, they do it again. To continue
a paused run instead, use POST /workflows/executions/{id}/resume.
The org is forwarded and voice scopes the lookup by it, so one tenant cannot restart another’s run.
A restart runs the workflow as it is NOW, with the original or new input.
When it has record steps or a record trigger, the key needs the object
scopes they exercise (403 missing_scopes), and only the workflow’s
owner or a graph8 admin may restart it, with reused or new input (403
owner_or_admin_required). When graph8 cannot confirm who is an admin the
restart is refused, never guessed: the workflow service answers 503, which
reaches the caller as 502 like its other upstream failures; retry later.
A skill with record inputs restarts under its run rules: a member must run it (403
record_inputs_need_a_member), the key needs the object scopes (403 missing_scopes) and an org key’s own
object grants must allow its objects (403 record_inputs_object_denied). It reads its records as the key’s
member, never an act-as member.
Authorizations
Parameters
Path Parameters
Execution id.
Execution id.
Header Parameters
Request Body
Optional restart overrides.
object
Responses
200
Successful Response
object
One voice object - a collection, an agent, a route, a chat.
Open-shaped: voice adds fields to these bodies on its own release cadence and a dropped-or-added key must not be a 500 in this service.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error