Verified against Semitexa Ultimate 2026.09.19.1020

Sync Events

Synchronous listeners execute inline before the response is sent. When you dispatch an event in sync mode, every registered listener completes its work before the HTTP response is returned to the client.

Event execution modesEvent execution modes. Event dispatcher: Receives one event. Sync listener: Runs before response. Deferred listener: Runs after response. Queued listener: Crosses durable transport. HTTP response: Waits for sync only. Queue worker: Handles durable workinlineafter responseenqueuecomplete firstconsumeEvent dispatcherReceives one eventSync listenerRuns before responseDeferred listenerRuns after responseQueued listenerCrosses durable transportHTTP responseWaits for sync onlyQueue workerHandles durable work
Event execution modes

How it works

The event dispatcher calls each sync listener in registration order within the current request lifecycle. The response is not flushed until all sync listeners have returned.

Why this matters

Sync execution guarantees that listener side effects are complete before the client sees the response. This is the right choice for validation side effects, required audit writes, or any work the response depends on. When the ledger runtime is enabled, propagated events are also written to the node ledger after sync listener execution.