Process Cross-Session Message
Reads and processes information that was provided by another journey
Description
Cross-session messages allow journeys to share info and create dependent flows. Before this step can be executed, another journey must create the message and provide the message ID to this journey. This step is used to look up the message using the ID, read the message content, mark the message as processed, and write response data to the processed message.
Once this step is completed, any journey that's waiting for the message to be processed will resume their flow and can access the additional response data. However, if the message has expired or has already been processed, the journey is aborted.
Configuration
| Field | Description |
|---|---|
| Cross-Session Message Reply Fields | A list of fields for the message response, which can be used by subsequent journey steps and any journey waiting for the message to be processed. The key is a parameter name and the value is an expression that yields the parameter value at runtime. |
| Output Variable | Name of the variable used to store the content of the processed message, which can be used in subsequent journey steps. Default is cross_session_message. It contains the message content (user_params) and message metadata (system_params). |
| Message ID | Expression yielding the message ID for this step, identifying the message to read and process. |
| Delete cross-session message after consumption | Determines if to delete the message immediately after it's processed or wait until it expires. Default is No. |