Skip to content
OTA-Pulse Docs

Retry Deployment

POST
/api/deployments/{deployment_id}/retry
 
curl --request POST \
  --url 'https://example.com/api/deployments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/retry?organization_id=2489E9AD-2EE2-8E00-8EC9-32D5F69181C0' \
  --header 'Authorization: Bearer <token>'

Retry a failed deployment.

Allowed only when the current status is FAILED. If retry_count has already reached 5 (the hard cap), the request is rejected with 422 ‘Max retries exceeded’.

On success resets the deployment to a fresh PENDING state:

  • status = PENDING
  • retry_count += 1
  • error_message = NULL
  • started_at = NULL
  • completed_at = NULL

Returns: 204 No Content on success.

Raises: HTTPException 404 if the deployment is not found or not owned by org. HTTPException 422 if the deployment status is not FAILED. HTTPException 422 if retry_count >= 5 (max retries exceeded).

Authorizations

Section titled “ Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “ Path Parameters ”
deployment_id
required
Deployment Id
string format: uuid

Query Parameters

Section titled “ Query Parameters ”
organization_id
required
Organization Id
string format: uuid

Responses

Section titled “ Responses ”

204

Section titled “ 204 ”

Successful Response

422

Section titled “ 422 ”

Validation Error

Media type application/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationError
object
ctx
Context
object
input
Input
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
Example generated 
{
  "detail": [
    {
      "ctx": {},
      "input": "example",
      "loc": [
        "example"
      ],
      "msg": "example",
      "type": "example"
    }
  ]
}