REST calls have different timeout values depending on operation. Which of the following is correct?

REST calls have different timeout values depending on operation. Which of the following is correct?

• A. 60 seconds for non-tracking, 180 seconds for tracking
• B. 120 seconds for non-tracking, 300 seconds for tracking/data retrieve
• C. 300 seconds for non-tracking, 120 seconds for tracking
• D. 120 seconds for both non-tracking and tracking

Answer: (B)

REST call timeouts reflect how long an operation is expected to take based on its complexity. Quick, non-tracking requests are treated as lightweight and are given a shorter timeout, while heavier operations such as tracking data retrieval can involve scanning large datasets and assembling results, so they’re allowed more time. Therefore, the standard mapping is a 2-minute timeout for non-tracking REST calls and a 5-minute timeout for tracking or data retrieval operations. If you’re dealing with large results, consider paging or asynchronous retrieval to avoid hitting the timeout.

REST call timeouts reflect how long an operation is expected to take based on its complexity. Quick, non-tracking requests are treated as lightweight and are given a shorter timeout, while heavier operations such as tracking data retrieval can involve scanning large datasets and assembling results, so they’re allowed more time. Therefore, the standard mapping is a 2-minute timeout for non-tracking REST calls and a 5-minute timeout for tracking or data retrieval operations. If you’re dealing with large results, consider paging or asynchronous retrieval to avoid hitting the timeout.