Skip to content

HTTP API Troubleshooting Topic: Retries to Iterable #6346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 26, 2024
+6 −0
Merged

HTTP API Troubleshooting Topic: Retries to Iterable #6346

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4eb4e9f
Update index.md
courtneyga Apr 3, 2024
29e225c
Apply suggestions from code review
stayseesong Nov 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/connections/destinations/catalog/iterable/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,12 @@ Iterable supports sending push notification events to Segment. These events are
They support the following events:
`Push Delivered`, `Push Bounced`, `Mobile App Uninstalled`, `Push Opened`

## High Retry Rate

If you are experiencing a large amount of retries within your destinations that are connected to your HTTP API source, this could be due to a related Etimedout errors. The errors seem to be Etimedout errors, in general, these are relatively normal intermittent problems that can come about when HTTP requests are made from server to server.

The Etimedout error is the result of an HTTP response not being received in a specific timeframe. Read more about how Segment retries events to destinations [here](/docs/connections/destinations/#retries-between-segment-and-destinations).


## Using Iterable with Engage

Expand Down