To handle long REST API calls in an Integration Procedure, which configuration helps specify a longer timeout?

To handle long REST API calls in an Integration Procedure, which configuration helps specify a longer timeout?

• A. Set the Timeout property on the HTTP Action in the Integration Procedure
• B. Configure a Remote action with timeout settings of 120000
• C. Check the Chainable checkbox on the integration procedure Action in the OmniScript
• D. Check the Chain on Step Check on the HTTP Action in the Integration Procedure

Answer: (B)

When a REST API call might take longer than the default wait time, you extend the wait by configuring the timeout on the external call itself. In OmniStudio Integration Procedures, this is done by using a Remote Action and setting its timeout in milliseconds, for example 120000. This makes the Integration Procedure wait up to two minutes for the API to respond, allowing slow endpoints to complete instead of timing out prematurely. The Remote Action is specifically designed to control how long the external call can run, so it directly affects the REST call duration. Other options relate to workflow behavior rather than adjusting how long the external request is allowed to run. If the API consistently takes longer, you can tune the timeout accordingly and consider additional patterns like retries or asynchronous processing as needed.

When a REST API call might take longer than the default wait time, you extend the wait by configuring the timeout on the external call itself. In OmniStudio Integration Procedures, this is done by using a Remote Action and setting its timeout in milliseconds, for example 120000. This makes the Integration Procedure wait up to two minutes for the API to respond, allowing slow endpoints to complete instead of timing out prematurely. The Remote Action is specifically designed to control how long the external call can run, so it directly affects the REST call duration. Other options relate to workflow behavior rather than adjusting how long the external request is allowed to run. If the API consistently takes longer, you can tune the timeout accordingly and consider additional patterns like retries or asynchronous processing as needed.