Next.js Article

Adapter Troubleshooting
for Marveo teams

Work through the most common adapter and connection issues before escalating to support.

Back to Next.js HelpTroubleshooting5 min read

Overview

Use this guide when the adapter appears to be installed correctly but connection health still looks wrong inside Marveo.

When to use this

  • The adapter appears installed but the workspace remains disconnected.
  • Deployments succeed but operational status is unhealthy.

Steps

  1. 1.Confirm the adapter version is compatible with the project.
  2. 2.Confirm required environment variables are set correctly.
  3. 3.Confirm workspace mapping points to the intended project.
  4. 4.Confirm deployment health and runtime parity.
  5. 5.Retry verification and capture logs before escalation.

Expected result

The root cause is either resolved locally or isolated with enough detail for a fast escalation.

If something goes wrong

  • If builds pass but status fails, suspect mapping or runtime config mismatch.
  • If health is intermittent, look for deployment instability or environment drift.
  • If the disconnect is persistent, confirm adapter registration reached the target environment.

Related article

Install Next.js Adapter

Set up the Marveo adapter so your Next.js project can connect to workspace operations.

Read article

Related article

Connect Next.js Site

Map your project to the right workspace so connection health and rollout checks can begin.

Read article

Related article

Deployment Environment Checklist

Check staging and production parity before onboarding, verification, or launch sign-off.

Read article