Signals

Deliver signals through the runtime or the service API. Target a run, not a graph node ID or output port.

await runtime.signal(
  runId,
  paymentReceived,
  receipt,
  idempotencyKey: 'payment-42',
);

HTTP:

POST /v1/workflow_runs/{run_id}/signals

The run ID may identify any generation in a continue-as-new chain. Delivery resolves the active generation. Duplicate keys do not append a second event.

Buffered signals that arrive before waitForSignal are applied when the await is reached.

See Also

• Signals vocabulary
• Service API