| Table of Contents | ||
|---|---|---|
|
This article provides an overview about how various connection timeouts work in the SnapLogic Platform.
Configuring the User Session Timeout Policy
As an Org admin, you can configure the session and idle timeouts in
...
Classic Manager for the users in your Org.
Navigate to Manager > Settings. Click User Session Timeout Policy to display the Configure Session Timeout dialog:
...
You can set the following timeouts with a value between 5–60 minutes. The default setting is 60 minutes.Session Timeout: Specify the session token duration, which determines how long the user session is valid.
Idle Timeout: Specify the client idle timeout to set how long the SnapLogic UI is open without any user activity.
Click Update.
You can communicate any changes in the session timeout policy by creating a User Notification.
Socket Timeout
The maximum socket timeout value
...
is, by default, set to 180 seconds. The platform waits a maximum of 180 seconds to receive data, after which the request times out.
The request timeout is inbound to SnapLogic, where Triggered or Ultra Pipeline requests are timed out when the requested resource does not complete and return within 15 minutes.
You can configure the socket timeout, which occurs when data is no longer received from the endpoint, by adding the following value (where n is the timeout value) to the
...
global
...
properties
...
:jcc.http_client_socket_timeout = n
Snap-specific Timeout
Some timeouts are specific to certain Snaps per the following:
The REST Snap Pack has its own timeout property. The timeout applies to both request and socket timeouts and only defines the timeout for the client being used. The receiver can end the request at any time on the receiver side and overwrite the timeout settings.
The Salesforce Snap Pack has a default timeout value of 600 seconds for both request and socket timeouts.
The SOAP Execute Snap enables you set a timeout on the Snap Settings tab.
Use an in-built HTTP clientFor the Task Execute and ForEach Snaps, as well as all internal Snaplex calls (such as registration or Snap downloads). You can configure the HTTP client timeout in the
...
global
...
properties
...
.
See Also
...