Requires the workflows:<name> entitlement for the execution. The mutating action queues receipt-backed rollback for a source workflow run, while a failed or canceled execution without a source run is marked rolled back immediately; Lambda restoration additionally requires a terminal execution with durable receipts.
/v1/executions/{id}/rollbackRequires the workflows: entitlement for the execution. The mutating action queues receipt-backed rollback for a source workflow run, while a failed or canceled execution without a source run is marked rolled back immediately; Lambda restoration additionally requires a terminal execution with durable receipts.
bearerAuth In: header
Execution ID.
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/executions/string/rollback"{ "execution": { "cancellationRequestedAt": "string", "createdAt": "string", "currentStage": "string", "executionId": "string", "finishedAt": "string", "principalId": "string", "status": "canceled", "workflow": "string" }}Cancel non-terminal execution POST
Requires the workflows:<name> entitlement for the execution and mutates only cancelable, non-terminal work. Lambda updates record a cancellation request, while other workflows cancel their run and execution; add-subdomain cannot be canceled after Route 53 has accepted its change.
Retry add-certificate finalization POST
Requires the workflows:add-certificate or workflows:onboard-domain entitlement matching the execution. This mutating recovery queues finalization only for a failed execution at its finalization stage with a source run and successful persisted prerequisite outputs; duplicate pending recovery is reused.