Optimove incident
Campaign execution - Some campaigns are in failed status
Optimove experienced a minor incident on January 24, 2026 affecting Batch Data Process and Batch Data Process, lasting 1h 47m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 24, 2026, 12:58 PM UTC
We have identified an issue causing a small percentage of campaigns to fail during execution. Please note that the majority of campaigns are proceeding successfully. Our team is currently executing a manual rerun for the affected campaigns. However, this recovery process will take some time to complete and risks campaigns going into "Not Run" status. Recommendation: If you have a high-priority campaign that has failed, we recommend manually re-running it immediately via the user interface (using the "Play" button in the campaign status window) rather than waiting for the backend recovery.
- identified Jan 24, 2026, 02:03 PM UTC
We are addressing execution errors affecting a limited number of campaigns. Due to potential delays and a risk of "Not Run" statuses, we advise manually triggering any high-priority campaigns via the UI for immediate delivery.
- monitoring Jan 24, 2026, 02:24 PM UTC
Backend recovery is underway and systems are stable. However, to avoid further delays while the queue clears, we continue to advise manually re-running any critical campaigns via the UI.
- resolved Jan 24, 2026, 02:46 PM UTC
The issue is resolved and systems are fully operational. Please verify your campaign statuses and manually run any campaigns that remain in "Not Run" or "Failed" status directly from the site.