Iterable: Issue With Dynamic Content For InApp Messages
Affected components: Global Campaign Sends
Timeline of updates
- resolved
Today, November 14th around 5:00 am PST, Iterable was alerted to an issue where inApp campaigns were not rendering handlebars correctly.
Iterable engineers began investigating the issue and identified the cause of the issue had started around 10:00 am PST on November 13th. Once they deployed their fix today at 7:30 am PST handlebars began rendering correctly again for all in App campaigns.
During this impact window customers may have also seen issues with in App messages not sending / being fetched correctly in regards to dynamic content not being available. If you have any additional questions or think you may have been impacted please reach out to support@iterable.com
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f713047701ad19d3…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Iterable, started 2024-11-14 17:45 UTC, resolved after 0 min, 1 update(s).
- Title
- Issue With Dynamic Content For InApp Messages
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/qkq9nsj1zvqw
Iterable profileRecent Iterable incidentsAll outages on November 14, 2024Iterable in November 2024MarkdownJSON