Extend Journey Expiration Time

Overview

The Extend Journey Expiration Time Action is used to change when the current Journey expires. By default, a Journey lasts 30 days. This default can be changed from Configuration Builder.

When a Journey is started, the user can return to it until it expires. For instance, if the user opens a Web Flow, leaves partway through, then returns to the same Canvas URL a few days later, the data they entered and the Web Page they were on will be retained. This behavior can be fine-tuned using the Extend Journey Expiration Time Action, the End Journey Action, and the Journey settings in the Configuration Builder.

Use Cases

• This Action can be used to customize the Journey behavior of a Chat Bot. For instance, if the user should start over in the Chat Bot flow after 1 day of inactivity, the Extend Journey Expiration Time Action could be used to set the Journey expiration time to 1 day in the future whenever the user sends a message.

• This Action could be used to modify the Journey expiration time based on the user state. For instance, if an App reaches a "Shipping Confirmation" Web Page, the Extend Journey Expiration Time Action could be used to ensure that the user can easily reach that Page even after several months have passed.

Action Properties

Set Journey Expiration Time

This property has two options:

To a Specific Time

When this is selected, the Journey will be set to expire at the Datetime provided.

Generally, you would use an Airscript Expression like:

ADD_TO_DATETIME(  
  NOW(),  
  1,  
  "day"  
)

This would set the Journey expiration time to exactly 1 day from now.

Relative To Current Expiration

When this is selected, the Journey's expiration time will be changed relative to where it is now.

For instance, if a Journey is set to expire 1 day from now, and the Extend Journey Expiration Time Action runs with "3 Days, Relative to Current Expiration", the new Journey expiration time will be 4 days from now.