Agile Platform Session Lifetime

The session is automatically created by Platform Server and depends on the channel used for the user interaction as described below.

Web Session Lifetime

The session starts during the first request the end-user establishes with Platform Server. By default, the session is identified by the URL path of the request. But you can use cookies to identify the session. How?

The session ends explicitly when the end-user logs-out, or automatically due to the session time-out; see Session time-out..

SMS Session Lifetime

The session is created when the end-user establishes the interaction with a specific number. The SMS interaction can be initiated by the end-user or through an iSMS notification. The session is identified by the tuple (originator phone, destination phone) as follows:

If there is no Session for the pair (originator, destination), then the tenant associated with the SMS request must be identified, as follows:

If there is only one tenant associated with the destination, then the tenant is immediately identified.
If there is more than one tenant associated with the destination phone number, then the keyword identifies the tenant, as specified in Service Center. In this situation, the pattern matching rules are used.

If the session already exists for the tuple (originator, destination), Platform Server immediately identifies the tenant, since there is already a context for that session.

The session ends explicitly when the end-user logs-out, or automatically due to the session time-out.

Web Services Session Lifetime

The session is created when the Web Service is invoked and lasts only for this request, which means that there is no persistency of the session between requests.

Timer Session Lifetime

The session is created when the Timer is invoked and lasts only for this request, which means that there is no persistency of the session between Timer executions.