Expo incident

Some EAS Workflows stuck in pending state

Major Resolved View vendor source →

Expo experienced a major incident on March 31, 2026 affecting EAS Workflows, lasting 49m. The incident has been resolved; the full update timeline is below.

Started
Mar 31, 2026, 01:40 PM UTC
Resolved
Mar 31, 2026, 02:30 PM UTC
Duration
49m
Detected by Pingoru
Mar 31, 2026, 01:40 PM UTC

Affected components

EAS Workflows

Update timeline

  1. investigating Mar 31, 2026, 01:40 PM UTC

    We're investigating an issue where some EAS Workflows are not progressing past the pending state. Affected workflows show no logs and remain queued. We'll provide updates as we learn more.

  2. resolved Mar 31, 2026, 03:52 PM UTC

    The issue has been resolved. A database table lock was preventing workflows from being picked up and progressing. The lock has been cleared and workflow processing has resumed. Affected workflows that were stuck during this period have been marked as errored with a message pointing to this status page. If your workflow was affected, please re-run it. We are continuing to investigate the root cause of the lock to prevent this from recurring.