Merge pull request #513 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/connections/destinations/catalog/webhooks/index.md

@@ -226,4 +226,4 @@ Under 'Connection Settings', you can provide up to 5 webhooks.
 
 ### Retries
 
-Our webhooks destination will retry any request that returns 5xx errors, multiple times, for a maximum of 4 hours.
+Segment retries requests that fail due to temporary errors like timeouts and 5xx status codes for up to four hours.

src/connections/functions/destination-functions.md

@@ -452,7 +452,7 @@ Yes, Functions access is logged in the [Audit Trail](/docs/segment-app/iam/audit
 
 ##### Does Segment retry failed function invocations?
 
-Segment retries 9 times over the course of 4 hours. This increases the number of attempts for messages, so Segment tries to re-deliver them another 4 times after some backoff. Segment doesn't retry if your function throws a [non-recoverable error](#errors-and-error-handling).
+Segment retries invocations that throw RetryError or Timeout errors for up to four hours. Segment does not retry if your function throws a [non-recoverable error](#errors-and-error-handling).
 
 ##### Are events guaranteed to send data in order?
 

src/connections/functions/source-functions.md

@@ -385,7 +385,7 @@ Copy and paste this URL into the upstream tool or service to send data to this s
 
 ##### What is the retry policy for a webhook payload?
 
-The webhook payload retries up to six times with an exponential backoff for the function in the event of a failure with the function. After six attempts, the message is dropped.
+Segment retries invocations that throw RetryError or Timeout errors up to six times. After six attempts, the request is dropped.
 
 ##### What is the maximum payload size for the incoming webhook?
 

src/partners/faqs.md

@@ -68,6 +68,4 @@ You can subscribe to updates [here](https://status.segment.com/).
 
 ### Does Segment retry data?
 
-Segment retries nine times over the course of four hours. This will increase the number of attempts for messages, so we'll try and re-deliver them another 4 times after some backoff.
-
-We don't retry anywhere which is the sign of an expired API key or failed payment. However, if we push bad code that results in a malformed payload and a 400 or 422 response from an endpoint, we also won't retry given that the call would not ever succeed.
+Segment retries requests for up to four hours if they fail due to temporary errors like timeouts, 429 Too Many Request status codes, and 5xx status codes. Segment does not retry requests that fail due to permanent errors like authentication failures or 4xx status codes.