​

Retry Task

​

Endpoint

POST /tasks/{task_uuid}/retry

​

Authentication

X-API-KEY: your-herodotus-cloud-api-key-here

​

Path Parameters

​

Example Request

curl -X POST https://staging.hdp.api.herodotus.cloud/tasks/01JPJ03YJT1A93D6NF56G4GVEQ/retry \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: your-herodotus-cloud-api-key-here"

​

Response

​

Success Response (200 OK)

{
  "message": "Task has been queued for retry",
  "status": "accepted",
  "uuid": "01JPJ03YJT1A93D6NF56G4GVEQ"
}

​

Not Found Response (404)

{
  "error": "Task not found",
  "uuid": "01JPJ03YJT1A93D6NF56G4GVEQ"
}

​

Bad Request Response (400)

{
  "error": "Cannot retry decommitment",
  "details": "Task results are missing. Cannot retry decommitment without results."
}

​

Unauthorized Response (401)

{
  "error": "Missing Herodotus Cloud X-API-KEY header"
}

​

Response Fields

​

Retry Behavior

​

Full Retry

• Dry run validation
• Chain proofs fetching
• Trace generation
• Atlantic proving
• Task decommitment

​

Decommitment-Only Retry

• 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 Received before 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