Solution skill
Iterable calls fail everywhere: wrong data center or missing identifier
Complete solution
Shows how to fix iterable calls fail everywhere: wrong data center or missing identifier. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
When Iterable API calls fail across the board, check which data center your account lives in. USDC and EUDC are separate instances with separate API hosts, and pointing at the wrong one fails everything.
Steps
- When Iterable API calls fail across the board, check which data center your account lives in. USDC and EUDC are separate instances with separate API hosts, and pointing at the wrong one fails everything. And every call needs at least one of email or userId: without an identifier there is nothing for Iterable to attach the event to.
When to use
You are seeing this: When Iterable API calls fail across the board, check which data center your account lives in. Use this skill when you run into "Iterable calls fail everywhere: wrong data center or missing identifier".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: RudderStack's open-source Iterable destination documentation FAQ: USDC and EUDC are geographically separated Iterable instances, and you must choose the data center matching your Iterable account region. Data cannot be shared between data centers. It also states that either email or userId is mandatory on every Iterable API call; without at least one identifier the destination throws.
Verified resolution: When Iterable API calls fail across the board, check which data center your account lives in. USDC and EUDC are separate instances with separate API hosts, and pointing at the wrong one fails everything. And every call needs at least one of email or userId: without an identifier there is nothing for Iterable to attach the event to.
Source URL: https://github.com/rudderlabs/rudder-transformer/blob/HEAD/src/v0/destinations/iterable/README.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_hl0nLBAKVPJ1tXqsE3iDLw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Iterable calls fail everywhere: wrong data center or missing identifier <span>— Vectle</span></a>