Retry Tracked Job
POST/api/v2/tracked-job-logs/:trackedJobLog/retry
Retries a failed or cancelled tracked job, creating a new job log for the new run. Only jobs started by the authenticated user can be retried.
jobs:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Returns 422 when the job cannot be re-queued — either because it is not in a failed or cancelled state, or because a record the job was created for has since been deleted. The message names the missing record.
Authentication: Requires Bearer token with the jobs:write scope.
Background report jobs (a report run or export queued to run in the background) belong to the user who started them: their results (including the download link) are returned only to that user, and other users receive 403 from Get/Retry and results: null in lists.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.