retry_instance

The cascade is not optional and has no flag, because retrying the root ALONE could never work: a call_workflow re-tick fail-fasts on its terminal child and a ForEach settle re-aggregates terminal children to the same verdict, both while answering 200. Where a run has no failed descendants this behaves exactly as it always did.

Because instances run on an immutable snapshot, this only makes forward progress when the original failure was transient (an external dependency that has since recovered); a config bug needs a re-publish and a fresh instance.

Path Parameters

Response Body

curl -X POST "https://example.com/instances/497f6eca-6276-4993-bfeb-53cbbbba6f08/retry"

{  "already_completed": 0,  "retried": 0,  "status": "running",  "ticked": 0,  "unretryable_cancelled": 0,  "unretryable_failed": 0}