Batch incident

CEP Automation triggers may stall in specific workflows

Minor Resolved View vendor source →

Batch experienced a minor incident on August 22, 2025, lasting 3d 21h. The incident has been resolved; the full update timeline is below.

Started
Aug 22, 2025, 09:11 AM UTC
Resolved
Aug 26, 2025, 06:56 AM UTC
Duration
3d 21h
Detected by Pingoru
Aug 22, 2025, 09:11 AM UTC

Update timeline

  1. resolved Aug 26, 2025, 06:56 AM UTC

    Aug 26, 06:56 UTC Resolved - The issue affecting automation workflows with Yes/No and/or Delay steps has been resolved. The fix has been successfully deployed and results have been monitored without further impact. All CEP Core Services (Email, Push, SMS delivery) are now operating normally. We apologize for the disruption and thank you for your patience. Aug 25, 07:48 UTC Monitoring - A fix for this issue has been implemented, we are now monitoring the results. Aug 22, 14:20 UTC Update - The fix is in testing and targeted for release early next week. Next update: Monday, August 25, by 18:00 CEST Aug 22, 09:11 UTC Identified - Impact: In some cases, automation workflows that include Yes/No steps and/or Delay steps can stall. Affected profiles remain stuck and may miss subsequent communications. Estimated impact: ~1% of users. Scope: Limited to automations using both Yes/No and/or Delay steps. Other automations are not affected. Current status: We have identified the defect and are developing a fix. No workaround is available at this time. Next steps: The fix will be deployed after validation. We apologize for the disruption and appreciate your patience.