Hold off auto-standby
Places a hold that prevents the auto-standby controller from putting the instance into standby before hold_until, and cancels any queued auto-standby attempt.
Each hold replaces the instance's previous hold, so hold_until always reflects the most recent call. Holding again after the policy's idle_timeout is shortened moves hold_until earlier.
Callers may use this before opening a connection to a candidate-idle instance: a 200 means it is safe to connect until hold_until; a 409 means the instance is in standby (or irrevocably entering it) and must be restored first.
Instances where auto-standby is disabled, unconfigured, or unsupported return 200 with their current status because no auto-standby will occur.
Path parameters
Instance ID or name
Response
Hold placed (or nothing to hold); safe to connect until hold_until
Example response
{
"supported": true,
"configured": true,
"enabled": true,
"eligible": true,
"status": "idle_countdown",
"reason": "idle_timeout_not_elapsed",
"idle_timeout": "5m0s",
"idle_since": "2026-04-06T17:04:05Z",
"last_inbound_activity_at": "2026-04-06T17:01:05Z",
"next_standby_at": "2026-04-06T17:09:05Z",
"hold_until": "2026-04-06T17:09:05Z",
"countdown_remaining": "4m0s",
"tracking_mode": "conntrack_events_v4_tcp"
}