Update Cross-Session Message
Updates information that's shared between different journeys running in parallel.
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. This step can then be used to extend the expiration or append data to the message. The data can be read by the journey that processes the message.
Configuration
| Field | Description |
|---|---|
| Ticket to update | Expression yielding the message ID for this step, identifying the message to update. |
| New Expiration | Period of time (in seconds) within which the message can be processed, counted from when the message was updated. This field is only evaluated in runtime. Note: Since the database will purge all messages after 3 days, the timeout cannot effectively be greater than 259,200 seconds, regardless of the configured timeout. |
| Attachment | Expression yielding the data to append to the message attachments. |