remove_resource_standby

Stop keeping a standby for one resource; the chat itself is untouched and the resource keeps its live chat.

Purpose

The standby row is forgotten and mirroring into it stops. Automatic failover can no longer swap this resource until a new standby is linked. Only the project owner may do this; a resource with no standby succeeds with nothing to remove.

This tool is annotated destructive: a client that supports the annotation asks a human before running it. The REST twin is DELETE /v1/projects/{project}/resources/{resource}/standby.

Required ability

project-recovery:delete

Input schema

{
    "type": "object",
    "required": [
        "resource_id"
    ],
    "properties": {
        "resource_id": {
            "type": "string",
            "description": "UUID of the resource whose standby to remove."
        }
    }
}

Output shape

{
    "data": {
        "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",
        "standby": null
    },
    "meta": {}
}

Example prompts

"Drop the standby on Signals; that spare channel is being repurposed."

Failure modes

  • VALIDATION_FAILED — the token is not the project owner's.
  • RESOURCE_NOT_FOUNDresource_id is not a resource the token can see.
  • AUTHENTICATION_REQUIRED — no authenticated user on the request.
  • TOKEN_MISSING_ABILITY — token lacks project-recovery:delete.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request