Xata: migration failed / branch hibernates during CI builds

TL;DR

If a Prisma migration fails, clear it with npx prisma migrate resolve with the rolled-back flag and the migration name, and run migrations on the direct (non-pooled) connection since advisory locks need it. A Xata branch hibernates when idle: add a keep-alive ping so prerender-heavy builds do not wake a sleeping branch mid-build. Check migration state with xata roll status, and complete a stuck in-progress roll with xata roll complete before starting a new one.

The error

migration failed / branch hibernates during CI builds

Fix

1. If a Prisma migration fails, clear it with npx prisma migrate resolve with the rolled-back flag and the migration name, and run migrations on the direct (non-pooled) connection since advisory locks need it. Expected: You get the expected result; the problem is gone.

2. A Xata branch hibernates when idle: add a keep-alive ping so prerender-heavy builds do not wake a sleeping branch mid-build. Expected: You get the expected result; the problem is gone.

3. Re-run the original operation and confirm the error is gone. Expected: no error, normal output.

When to use

• You hit this exact error with Xata.
• The symptom matches: migration failed / branch hibernates during CI builds.

When NOT to use

• A different error message from Xata; the cause here is specific to this error.
• Unrelated Xata issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Xata. Source: https://github.com/distilled-mirror/spec-mirror-xata/blob/HEAD/specs/docs/automations/ga-pr.md.

Variant phrasings

migration failed / branch hibernates during CI builds

Why it happens

Prisma migrations against a Xata branch fail, or builds hit a sleeping branch. Two separate issues with separate fixes.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/distilled-mirror/spec-mirror-xata/blob/HEAD/specs/docs/automations/ga-pr.md

Source: Prisma migrations against a Xata branch fail, or builds hit a sleeping branch. Two separate issues with separate fixes.

Verified resolution: [field troubleshooting]: if a Prisma migration fails, clear it with npx prisma migrate resolve with the rolled-back flag and the migration name, and run migrations on the direct (non-pooled) connection since advisory locks need it. A Xata branch hibernates when idle: add a keep-alive ping so prerender-heavy builds do not wake a sleeping branch mid-build. Check migration state with xata roll status, and complete a stuck in-progress roll with xata roll complete before starting a new one.

Source URL: https://github.com/distilled-mirror/spec-mirror-xata/blob/HEAD/specs/docs/automations/ga-pr.md