A developer needs to retrieve data from an external system that stores policy dat a. The external system supports REST APIs to access and update…

The scenario involves a two-level call: an OmniScript calls an Integration Procedure (IP), which in turn calls a slow external REST API. To prevent failures, timeouts must be managed at both levels.

1. Integration Procedure Level (HTTP Action): Setting the Timeout property on the HTTP Action (Option A) within the IP is crucial. This defines how long the IP will wait for the external system to respond before the callout itself times out, allowing for graceful error handling within the procedure.

2. OmniScript Level (Remote Action): The OmniScript's call to the IP is a remote action with a default timeout of 30,000 ms. Since the external system can be slow, this default may be insufficient. Configuring the remote action's timeout to a higher value, such as the maximum 120,000 ms (Option C), prevents the OmniScript from timing out while waiting for the IP to complete its long-running task.

1. Salesforce Help

Integration Procedure HTTP Action Properties: The Timeout property for an HTTP Action is specified in milliseconds. "If a response is not received in the specified time

the call is terminated." This directly supports setting a timeout on the HTTP Action itself. (Reference: Salesforce Help

"HTTP Action for Integration Procedures"

Section: HTTP Action Properties).

2. Salesforce Help

OmniScript Integration Procedure Action Properties: The timeout remote option for an Integration Procedure Action in an OmniScript specifies the client-side timeout in milliseconds. The default is 30000

and the maximum is 120000. This is necessary to prevent the OmniScript from timing out before the Integration Procedure can finish. (Reference: Salesforce Help

"Integration Procedure Action"

Section: Remote Options).

3. Salesforce Help

Chainable Server-Side Calls in OmniScripts: "To prevent Apex governor limits

you can designate server-side calls within an OmniScript as chainable... Chainable calls are queued and executed in the order they are made." This confirms Chainable's purpose is managing multiple calls

not a single call's timeout. (Reference: Salesforce Help

"Enable Chainable Server-Side Calls in OmniScripts").