How many retries are performed by default for GET and DELETE methods when a Remotely Closed error occurs in the HTTP Requester?

How many retries are performed by default for GET and DELETE methods when a Remotely Closed error occurs in the HTTP Requester?

• A. 1
• B. 3
• C. 2
• D. 4

Answer: (B)

This question is about how the HTTP Requester handles transient network failures. When a Remotely Closed error occurs, the built-in retry mechanism kicks in for idempotent methods like GET and DELETE. By default, it will try again three times after the initial attempt. In practice this means up to four total attempts: the original request plus three retries. This approach helps recover from short network hiccups without causing duplicated side effects, since GET and DELETE are considered safe to retry. If you need to change this behavior, you can adjust the retry policy in the HTTP Requester configuration.

This question is about how the HTTP Requester handles transient network failures. When a Remotely Closed error occurs, the built-in retry mechanism kicks in for idempotent methods like GET and DELETE. By default, it will try again three times after the initial attempt. In practice this means up to four total attempts: the original request plus three retries. This approach helps recover from short network hiccups without causing duplicated side effects, since GET and DELETE are considered safe to retry. If you need to change this behavior, you can adjust the retry policy in the HTTP Requester configuration.