transition_v2_workspace_reset

Quiesce, settle and resume change the bound workspace's maintenance state or settle fenced work. Quiesce and settle require the exact current signed preparation. The numeric expiresAt in the illustration is an example. Substitute the prepared expiry and keep the exact key and target for reconciliation.

These signatures come from local MCP tool discovery. Use the signature registered by your deployment and confirm your identity and permissions before calling the tool.

Endpoint signatures and example arguments

Examples show the arguments to the tool. Replace placeholder IDs and illustrative revisions with values from your authorized disposable scope.

{
  "program": {
    "languageVersion": 2,
    "function": "workspace.reset.quiesce",
    "arguments": {
      "manifestDigest": "{{manifest_digest}}",
      "expiresAt": 1793980800,
      "signature": "{{prepared_signature}}"
    }
  },
  "idempotency_key": "docs-example-0001"
}

{
  "properties": {
    "program": {
      "additionalProperties": true,
      "title": "Program",
      "type": "object"
    },
    "idempotency_key": {
      "title": "Idempotency Key",
      "type": "string"
    }
  },
  "required": [
    "program",
    "idempotency_key"
  ],
  "title": "transition_v2_workspace_resetArguments",
  "type": "object"
}

Handling errors

MCP_TOOL_CAPACITY_NOT_DISPATCHED means the server did not dispatch this call. MCP_TOOL_DEADLINE_OUTCOME_UNKNOWN or MCP_TOOL_PROCESS_FAILED_OUTCOME_UNKNOWN leaves the outcome unknown. For a call with effects, reconcile the original request before starting a new one. For a scoped denial, verify the caller's grant and the selected target.

Module guidelines · Related workflow · Application-language function catalog