Skip to main content
all is the default handler completion mode. The event completes only after every matching handler reaches a terminal state.

Lifecycle impact

  1. All matching handlers are allowed to run.
  2. A successful early handler does not short-circuit the event.
  3. Event completion waits for every handler to finish, fail, or time out.
  4. Result collection includes all successful non-None / non-undefined return values.

Execution order example

Notes

  • all is best when multiple handlers contribute required side effects.
  • Handler scheduling (serial vs parallel) changes overlap, but not the fact that all handlers must settle.