Events

Replay a recorded callback

Forwards a callback the run received to its connector route again, exactly as recorded, to prove the application handles a repeat. The event must be a callback.received on a resource with a connector route and the run must be active. The replay is recorded as callback.replayed, then travels like any delivery: the timeline shows its own callback.forwarded and connector.request.completed against the original event id. Armed faults do not act on a replay; it is the test's explicit act. At most 200 replays per run. Needs rig.run.

post/v1/runs/{runId}/events/{eventId}/replay

Request

  • Base URL: https://api.ironfang.com/rig
  • URL: https://api.ironfang.com/rig/v1/runs/{runId}/events/{eventId}/replay
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Response

The replay is queued for the route

delivery_idstring uuid required

The delivery the connector will receive; its completion event names it.

Example response

{
  "event": {
    "type": "resource.allocated"
  }
}

Changes

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