paperclipai/paperclip · error

Workspace is not ready to publish (${gate.reason}${gate.deta

Error message

Workspace is not ready to publish (${gate.reason}${gate.detail ? `: ${gate.detail}` : ""})

What it means

The protected managed-workspace readiness gate (own database, cloned rows, login handoff, identity match) evaluated to not-ok; the workspace is refused publishing as running/healthy and the rejection is logged with gate reason/detail.

Source

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

      });
      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}` : ""})`,
          );
        }
      }
    }
    record.status = "running";
    record.healthStatus = "healthy";
    record.lastUsedAt = new Date().toISOString();
    record.stoppedAt = null;
    const serviceOutputExcerpt = await readServiceOutputExcerpt();
    if (serviceOutputExcerpt && input.onLog) {
      await input.onLog("stdout", `[service:${serviceName}] ${serviceOutputExcerpt}`);
    }
    await touchLocalServiceRegistryRecord(record.serviceKey, {
      runtimeServiceId: record.id,
      lastSeenAt: record.lastUsedAt,
    });
  }).catch(async (err) => {

View on GitHub (pinned to a7e689b3c3)

Solutions

1. Read the logged gate.reason/gate.detail to identify which readiness subject failed
2. Fix the failing subject (database clone, login handoff, identity match) and let the readiness probe re-run
3. Verify workspace and instance identity fields agree
4. Re-provision the workspace if cloned rows are missing

When it happens

Trigger: Thrown at server/src/services/workspace-runtime.ts:6038 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/08f17fd31668734c. Report an issue: GitHub.