WaitStable

Wait for platform events

Creates a collection barrier: the process waits until the selected platform event has been received for every resource in the collection.

Collection + event

Wait for platform events

Suspension durable

Received events

Vue d’ensemble

Creates a collection barrier: the process waits until the selected platform event has been received for every resource in the collection.

Exemple

After creating several credit notes, wait until each has reached the expected business state before continuing an aggregated operation.

Key point Waiting for an event does not start a new process: it suspends the current instance, then resumes the same context when correlation is satisfied.

Parameters 2

continuation_modeRequisenum

Presentation mode for the wait in a User Journey. foreground favors a short visible wait before degrading to background; background immediately presents an external wait that may take longer.

event_typeRequisenum

Expected platform-event type. Its selection also determines the available correlation resources and business outputs.

Outputs 1

eventevent[]

Collection of platform events that satisfied the barrier for the expected resources.

Behavior

Install correlation

The editor derives the expected collection type from the event contract. Each resource in the collection is correlated separately; an empty collection satisfies the barrier immediately.

Suspendre l’instance

If the expected event is not yet available, the node enters a durable wait. The instance remains observable during this period.

Resume on the event

The output contains the collection of events that satisfied the barrier, plus typed projections derived from the event contract.

Key point Presentation options such as foreground/background control how the wait appears in the User Journey; they do not change the business correlation contract.

Limits and responsibilities

Correlation that is too broad can resume the process on an event that does not represent the expected case; map the discriminating objects available.
The barrier waits for every resource in the initial collection; it does not become open-ended monitoring for new resources added later.
To start a new instance from an event, use a launcher rather than a wait node.

Troubleshooting

If the instance remains waiting, first check the event type and then the correlation values actually stored on the node.
Then verify in the event catalog that the expected event actually exposes the resource or object used for correlation.
For a wait visible in a User Journey, also check the selected continuation mode.