WaitStable

Wait for platform event

Suspends the process until the next platform event of the selected type for the explicitly correlated resource.

Correlation + event

Wait for platform event

Suspension durable

Received event

Vue d’ensemble

Suspends the process until the next platform event of the selected type for the explicitly correlated resource.

Exemple

After issuing an invoice, wait for invoice.paid for that exact invoice before continuing a fulfillment step.

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

Event that resolved the wait, exposed under the common.event contract.

Behavior

Install correlation

After selecting the event type, the editor exposes correlation objects compatible with its contract. At least one resource must be mapped so the wait cannot capture an event unrelated to the instance.

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 node returns the received event along with the business projections declared by its 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 node resumes on the next matching event; it does not aggregate complete event history.
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.