Optimove incident

US | Batch Update Process - Delay in Campaign execution

Major Resolved View vendor source →

Optimove experienced a major incident on July 4, 2026 affecting Batch Data Process and Track & Trigger, lasting 6h 28m. The incident has been resolved; the full update timeline is below.

Started
Jul 04, 2026, 12:15 PM UTC
Resolved
Jul 04, 2026, 06:43 PM UTC
Duration
6h 28m
Detected by Pingoru
Jul 04, 2026, 12:15 PM UTC

Affected components

Batch Data ProcessTrack & Trigger

Update timeline

  1. investigating Jul 04, 2026, 12:15 PM UTC

    We are currently experiencing errors leading to delays in campaign execution. As a result, some campaigns may remain in a “Not Run” status. This typically occurs when the Batch Data Update is delayed and campaign execution starts later than scheduled, causing some campaigns to miss their designated run time. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option. https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period. https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run. To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

  2. investigating Jul 04, 2026, 12:16 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 04, 2026, 01:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jul 04, 2026, 06:36 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jul 04, 2026, 06:43 PM UTC

    This incident has been resolved.