Optimove incident

Campaign execution - Some campaigns are in failed status

Minor Resolved View vendor source →

Optimove experienced a minor incident on January 24, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 24, 2026, 02:46 PM UTC
Resolved
Jan 24, 2026, 02:46 PM UTC
Duration
Detected by Pingoru
Jan 24, 2026, 02:46 PM UTC

Update timeline

  1. monitoring Jan 24, 2026, 02:46 PM UTC

    Jan 24, 14:46 UTC Resolved - 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. Jan 24, 14:24 UTC Monitoring - 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. Jan 24, 14:03 UTC Identified - 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. Jan 24, 12:58 UTC Investigating - 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.