Recreate a non-functional scope

If an agent-backed scope becomes non-functional due to infrastructure issues, you can trigger a recreation to restore it. This works for any agent-backed scope, regardless of the underlying provider.

Important:

• Recreating a scope causes downtime.
• It may leave behind residual or unstable infrastructure.
• The recreated scope is not automatically deployed, so you need to deploy it manually after the process.

How it works

Recreating a scope attempts to delete the broken scope and its associated infrastructure, and then creates a new scope using the same configuration.

The newly created scope:

• Uses the same scope ID and slug.
• Retains the same configuration as the original.
• Preserves its custom domain and DNS settings, if configured.

Recreate a scope

1. Trigger the recreation

Use the UI, CLI, or API to start the recreation.

UI

1. Go to Development > Scopes.
2. Click Actions > Recreate for the scope you want to recreate.

CLI

Patch the scope's status to recreating:

np scope patch --id "$SCOPE_ID" --body '{"status": "recreating"}'

cURL

Send a PATCH request to set the scope's status to recreating:

curl -L -X PATCH 'https://api.nullplatform.com/scope/:id' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <token>' \
-d '{
  "status": "recreating"
}'

2. Deploy the recreated scope

Once the recreation completes, you need to redeploy the scope to make it functional:

1. Go to Development > Scopes.
2. Click Deploy for the scope you just recreated.