Replay Job As New V1
Re-run a succeeded job with the same params. Distinct from /retry, which is reserved for failed/cancelled jobs…
POST
Re-run a succeeded job with the same params.
Distinct from
/retry, which is reserved for failed/cancelled jobs.
This is the right call for ‘re-fetch this dataset’ / ‘regenerate this
report’ workflows where the original task was successful but the
output is now stale. Quota-checked; original job remains intact.
Idempotency. Pass an Idempotency-Key header to make the replay
replay-safe: a duplicate POST returns the original new-job id with
Idempotency-Replayed: true. Per-source-job key namespace so the
same caller key is reusable across different sources.
Path parameters
string (uuid)
required
Response
TriggerResponse
string
required
UUID of the queued job. Use it for subsequent /jobs/:id calls.
string
required
Initial job status — usually ‘queued’. Replays of an idempotent request return the existing job’s current status.