paperclipai/paperclip · error

Managed workspace readiness gate could not resolve the contr

Error message

Managed workspace readiness gate could not resolve the control-plane database

What it means

The managed-workspace readiness gate passed but record.db is unset, so the publish path has no control-plane database handle for the workspace; the readiness contract requires an own database before publishing healthy.

Source

Thrown at server/src/services/workspace-runtime.ts:6023

    // Transport readiness only proves a listener answered. A managed workspace
    // must additionally satisfy the protected readiness contract — own database,
    // cloned rows, login handoff, and matching instance/workspace identity —
    // before it may be published as running/healthy (PAP-17572).
    if (managedWorkspaceIdentity) {
      const publishHealthUrl = resolveRuntimeServiceHealthUrl(
        record.port ? `http://127.0.0.1:${record.port}` : rewriteUrlHostToLoopback(record.url ?? backendUrl),
        { serviceName, command },
      );
      if (!publishHealthUrl) {
        throw new Error("Managed workspace readiness gate could not resolve a health URL");
      }
      let gate = await waitForManagedWorkspaceReadiness({
        healthUrl: publishHealthUrl,
        identity: managedWorkspaceIdentity,
      });
      if (gate.ok) {
        if (!record.db) {
          throw new Error("Managed workspace readiness gate could not resolve the control-plane database");
        }
        gate = await probeManagedWorkspaceHandoffSubjects({
          db: record.db,
          healthUrl: publishHealthUrl,
          identity: managedWorkspaceIdentity,
        });
      }
      if (!gate.ok) {
        logManagedWorkspaceReadinessRejection({
          executionWorkspaceId: managedWorkspaceIdentity.executionWorkspaceId,
          healthUrl: publishHealthUrl,
          result: gate,
        });
        if (shouldBlockPublicationOnReadiness(gate)) {
          throw new Error(
            `Workspace is not ready to publish (${gate.reason}${gate.detail ? `: ${gate.detail}` : ""})`,
          );
        }

View on GitHub (pinned to a7e689b3c3)

Solutions

1. Verify workspace database provisioning produced a db handle on the record
2. Check provisioning logs for a failed/cloned-database step
3. Re-provision the managed workspace
4. Inspect prior gate logs (PAP-17572 context) for the dropped db handle

When it happens

Trigger: Thrown at server/src/services/workspace-runtime.ts:6023 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of paperclipai/paperclip@a7e689b3c3 (2026-08-21). Data as JSON: /api/errors/7cccc1e38655e0a6. Report an issue: GitHub.