Triggers & events

Two different things get called “events.” They are not the same.

Starting work

Something has to create an execution: a client call, an HTTP request, a schedule, a queue message. Those entry points are triggers.

The trigger surface — webhooks, cron, queues, and how they attach to programs — is still being reconciled with Programs and Executions. This page does not document routes, schedules, or enqueue APIs that have not settled.

What will stay true: a trigger starts an execution. It is not how a running execution waits.

Waiting inside an execution

A running program waits with waitForEvent:

await waitForEvent("approved");

That parks the execution until a matching signal arrives. After restore, the wait is still the wait. Sending the event continues this execution. It does not start a new one.

The intended client shape is run.send(name, payload). The exact API is not frozen yet.

See Durable operations for waitForEvent itself.