Troubleshooting Article

Next.js Connection Stuck in Pending
without guesswork

Check the adapter, environment, and workspace mapping when a Next.js site will not move past pending status.

Back to TroubleshootingNext.js4 min read

Overview

Pending status usually points to adapter detection issues, environment mismatch, or a workspace mapping problem rather than a UI issue.

When to use this

  • The Next.js site never reaches connected or healthy status.
  • The adapter appears installed but the workspace does not update.

Steps

  1. 1.Confirm the adapter install and version compatibility.
  2. 2.Confirm environment variables are present in the correct environment.
  3. 3.Confirm the workspace is mapped to the intended project.
  4. 4.Compare deployment health between staging and production.

Expected result

The pending state clears or the root cause is narrowed enough for a precise escalation.

If something goes wrong

  • If builds pass but status stays pending, inspect mapping and runtime config.
  • If the behavior differs between environments, review parity before retrying.

Related guide

Deployment Environment Checklist

Open guide