Post v0 city by city name session by ID wake

Records an explicit wake and asks the controller to start the session; the API never starts the runtime itself. 409 wake-will-not-start means the wake is recorded but the controller will not act on it (no runnable template, a dependency-only or drained pool session, a suspended city, rig or agent, a demand-only singleton, an abandoned create, an open circuit breaker, a startup-health quarantine, or an idle latch); the detail names the remedy. gc session wake applies the same rules.

post/v0/city/{cityName}/session/{id}/wake

Request

  • The document declares no server URL.
  • Auth: none declared. Required headers: X-GC-Request

Path parameters

cityNamestring required

City name.

idstring required

Session ID, alias, or runtime session_name.

Headers

X-GC-Requeststring required

Anti-CSRF header required on mutation requests. Any non-empty value is accepted; the header's presence is what the server checks.

Response

OK

idstring

Resource ID.

statusstring required

Operation result.

Example response

{
  "status": "ok"
}

Changes

No recorded changes to this operation across all 50 revisions of this API.