Expo: Some EAS Workflows stuck in pending state

What to do

Check whether you use Expo EAS Workflows. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 50m it lasted.
Anything that failed between 2026-03-31 13:40 UTC and 2026-03-31 14:30 UTC may need a replay.
Subscribe to Expo's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=expo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingMar 31, 2026, 1: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.
provider
resolvedMar 31, 2026, 2:30 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.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Expo still down?

No, this incident was resolved 2026-03-31 14:30 UTC. For Expo's live state, see https://down.guide/expo.

How long did it last?

50m, from 2026-03-31 13:40 UTC to 2026-03-31 14:30 UTC, by the times Expo posted.

What was affected?

Expo named EAS Workflows.

What caused it?

Expo hasn't published a root cause. If it does, it shows here.

Where does this come from?

Expo's official status page, https://status.expo.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.