Pipelines

Re-dispatch a previous dispatch

Creates a NEW dispatch row inheriting the original's frozen selection, projection, watermark and data product (replay_of points back at it), and publishes fresh events — new dedup keys, new idempotency keys — to whatever bindings match NOW. The original row is untouched.

A re-dispatch is a new row, not a re-publish, because the outbox suppresses a duplicate dedup_key: re-publishing the same dispatch would be a no-op. The payload is identical (the selection is frozen), so a receiver sees the same records with a new delivery identity. Requires write scope.

post/v1/pipelines/{id}/dispatches/{dispatchId}/redispatch

Request

  • Base URL: https://api.talonic.com
  • URL: https://api.talonic.com/v1/pipelines/{id}/dispatches/{dispatchId}/redispatch
  • Auth: HTTP bearer

Path parameters

idstring uuid required
dispatchIdstring uuid required

Response

The new dispatch row.

dispatch_idstring uuid required
grain'row' | 'pipeline' | 'assembly' | 'matcher' | 'data_product' required

What one deliverable is — set by the node, not by the caller.

status'pending' | 'published' | 'empty' | 'failed' | 'superseded' | 'skipped' required

skipped = the submitting POST /v1/run request's dispatch / bindings controls suppressed this node (no events; terminal, not re-dispatchable).

record_countinteger required

Records the dispatch froze.

event_countinteger required

Outbox events published (chunks for a collection grain, one per record for row grain).

existingboolean

Present on the trigger route — true when the Idempotency-Key matched an earlier dispatch (returned with 200; nothing was published again).

errorstring

Present only when status is failed.

replay_ofstring uuid

The dispatch whose frozen selection this one inherited.

Changes

No recorded changes to this operation across all 1 revision of this API.