Retry Task
Retries a failed HDP task. For tasks that failed at decommitment stage (TaskDecommitmentFailed), only the decommitment step will be retried. For other failed tasks, the entire workflow will be retried from the beginning. This endpoint requires authentication.
Endpoint
Authentication
This endpoint requires authentication using an API key:Path Parameters
| Parameter | Type | Description |
|---|---|---|
| task_uuid | string | The unique identifier (UUID) of the task to retry |
Example Request
Response
Success Response (200 OK)
Not Found Response (404)
Bad Request Response (400)
For decommitment retry without results:Unauthorized Response (401)
Response Fields
| Field | Type | Description |
|---|---|---|
| message | string | Success message |
| status | string | Status of the request (always “accepted”) |
| uuid | string | The unique identifier of the task |
| error | string | Error message (only present in error responses) |
Retry Behavior
Full Retry
For tasks that failed at any stage exceptTaskDecommitmentFailed, the entire workflow will be retried:
- Dry run validation
- Chain proofs fetching
- Trace generation
- Atlantic proving
- Task decommitment
Decommitment-Only Retry
For tasks with statusTaskDecommitmentFailed, only the decommitment step will be retried:
- The task results must be available
- Trace generation and Atlantic proving steps are skipped
- Only the decommitment workflow is executed
Notes
- Authentication is required for this endpoint
- The task status will be reset to
Receivedbefore retry - For decommitment-only retries, the task results must be present
- The retry will create a new task execution in the queue
- Use this endpoint to recover from transient failures

