Vercel check suite stuck queued with no Preview deployment for PR commit

Help
,
1

Hi Vercel team,

Vercel’s GitHub integration created a check suite for an exact PR commit, but processing stopped before a check run or Preview deployment was created.

Project: yo-joe-vault
Repository: cstephenson150/yo-joe-vault
PR: #231
Branch: codex/catalog-dual-image-create-implementation
Commit: 00317b998ff3e4978531fdad0c4f828f318fde47
GitHub check-suite ID: 83551538061
Vercel GitHub App ID: 8329
Suite created and last updated: 2026-08-03T12:40:51Z

Current behavior:

  • The Vercel-owned check suite remains queued with no conclusion.

  • The suite is marked rerequestable and runs_rerequestable.

  • It contains zero check runs.

  • GitHub shows the required Vercel check as “Expected — Waiting for status to be reported.”

  • No Vercel commit status exists for this SHA.

  • No GitHub deployment exists for this SHA.

  • No deployment—queued, building, ignored, failed, or otherwise—exists in the Vercel dashboard for this SHA.

  • The PR’s GitHub Actions checks completed successfully.

The preceding commit, ef223698bb048766982cbf61b72d440af54d6e88, created its Preview deployment and Vercel checks normally. The repository, project root, production branch, and Vercel Git integration have not changed since then.

I also confirmed:

  • The GitHub App is associated with the correct repository.

  • Automatic Git deployments remain enabled.

  • No Ignored Build Step is configured.

  • No vercel.json disables Git deployments.

  • .vercelignore does not exclude the changed files.

  • The project is not configured as a monorepo.

  • The commit author identity matches the preceding successful commit.

One attempt to re-request GitHub check suite 83551538061 through the GitHub API returned HTTP 404. It was not retried. The current GitHub CLI OAuth credential does not provide the Checks-write credential type required for that operation.

I attempted to open an official Vercel support case under CI/CD > Git Providers, but the support form required a Deployment URL. The issue is that no deployment was created, so there is no valid exact-commit Deployment URL to provide. I did not substitute an older deployment.

Could a Vercel team member inspect the Git-integration processing for this suite and commit?

The desired recovery is:

  • Resume or recreate the Preview deployment for exact commit 00317b998ff3e4978531fdad0c4f828f318fde47.

  • Create only a Preview deployment—not Production.

  • Attach the required successful Vercel check to that same commit.

  • Avoid requiring a replacement commit or repository configuration change.

Please let me know if additional non-sensitive identifiers would help diagnose where processing stopped.

Thank you.

2

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.