Iterable incident
Embedded Messaging Send Skips are Impacting Customers
Iterable experienced a minor incident on August 1, 2025 affecting SMS Sends and Global Campaign Sends, lasting 4h 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 01, 2025, 08:32 PM UTC
We are currently investigating an increase in embedded Messaging skips, which appears to be impacting most customers. Other sends globally are not impacted. Our team is actively working to identify the root cause of this issue. Next Update: We will provide our next update by 2:00 PM PDT.
- investigating Aug 01, 2025, 08:34 PM UTC
We are continuing to investigate this issue.
- identified Aug 01, 2025, 09:06 PM UTC
The issue with embedded messages incorrectly being send skipped has been identified and the team is actively working to remediate it. We have confirmed that the impact is only to embedded messages triggered by Journeys. The aforementioned remediation should be completed shortly and we will continue to monitor that no further send skip issues occur once complete. Next update: We will provide our next update at 3:00 PM PDT.
- identified Aug 01, 2025, 09:59 PM UTC
The send skip behavior for journey triggered embedded messages has been resolved. The team is still working on validating that the remediation has restored full functionality. Next update: We will provide our next update at 4:00 PM PDT.
- identified Aug 01, 2025, 11:01 PM UTC
During the validation of the remediation, the team identified that another fix was necessary to fully restore the functionality of journey triggered embedded messages. They are working on testing and releasing the fix. Next update: We will provide our next update at 6:00 PM PDT.
- identified Aug 02, 2025, 01:03 AM UTC
The additional fix has been tested successfully and deployment is in progress. This process will take another 15-30 minutes to rollout to all customers. This will fully restore functionality for journey triggered embedded messaging, which were the only sends impacted. Next up: Our next update will be at or before 7:00 PM PDT.
- resolved Aug 02, 2025, 01:27 AM UTC
This incident has been resolved and functionality has been fully restored for journey triggered embedded messaging sends. If more information is needed, please reach out to [email protected]. This will be the final update.