WaitStable

Wait for extension event

Suspends the process until a matching extension event is received for the configured type and correlations.

Correlation + event

Wait for extension event

Suspension durable

Received event

Vue d’ensemble

Suspends the process until a matching extension event is received for the configured type and correlations.

Exemple

After starting a provider check, wait for its result event without creating a polling loop in the process.

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 7

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_typeRequisstring

Exact identifier of the extension event to wait for, for example extension.<extension>.<event>.

extension_config_idOptionnelref(extension_config)

Optional extension configuration used to restrict the wait to one precise provider/configuration.

external_objectOptionnelobject

Known external object whose identity is used to correlate the expected event.

external_object_typeOptionnelstring

External-object type to correlate when no complete external object is available.

external_object_idOptionnelstring

External identifier to correlate with the expected event.

subjectOptionnelAgent memory

Typed platform object used for correlation. The node derives its resource type and identifier automatically.

Outputs 3

eventevent

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

extension_eventobject

View of the received extension event, usable when the process needs provider-specific data.

associated_companiesobject[]

Associated companies projected by the event when the extension can identify them.

Behavior

Install correlation

Correlation may rely on the extension configuration, an external object, or the typed platform object supplied as subject. Specify only criteria that genuinely identify the expected event.

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 received extension event and business outputs declared by its contract become available when the wait resolves.

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.