Skip to main content

Diagnose your scope

You can run Diagnose directly from the nullplatform UI to quickly understand why a scope is not behaving as expected. Running Diagnose does not change your scope or your cluster. It only inspects the current state and reports findings.

Where to find Diagnose

Diagnose is available as an action on agent-backed scopes.

To run it:

  1. Go to Development > Scopes.
  2. Select the scope you want to diagnose and open the Actions menu.
  3. Click Diagnose.

This opens the Diagnose view and starts a new run immediately.

Rerun Diagnose at any time

After you apply a fix, redeploy the scope first. Once the new deployment is live, you can rerun Diagnose to confirm the issue is resolved.

What happens after you click Diagnose

Once the run starts, Diagnose executes a series of checks on networking, the scope itself, and services, and shows progress in real time.

Each section represents a different area of the system and runs its checks independently. This makes it easy to see which part of the scope is healthy and where issues are concentrated.

Inspecting checks and logs

When you open a check, you can:

  • See what the check validated
  • Review why it passed or failed
  • Inspect logs collected during execution

Logs are especially useful when a check fails. They give you concrete evidence to understand the root cause and decide what to do next.

What Diagnose does not do

Running Diagnose does not modify resources, restart workloads, or block deployments. It is safe to run as often as needed.