Bench is in error


`type`	`https://docs.frem.sh/reference/api/errors/bench-in-error`
HTTP status	`409` Conflict

What it means

The bench is in the error state because a lifecycle step, usually a suspend, failed part-way. The machine may still be running and billing. Whether it still holds your profile disk is uncertain, so the owner’s suspend request is refused rather than guessed at.

Example detail messages returned with this error:

The bench is in error after a failed lifecycle step and cannot take a suspend request. An organisation admin can retry the suspend from the Benches admin page or with POST /api/v1/orgs/{org}/frembench/benches/{id}/force-suspend.

What to do

Ask an organisation admin to press Retry suspend on the organisation’s Benches admin page, or to call POST /api/v1/orgs/{org}/frembench/benches/{benchId}/force-suspend with a seats:write token. That hands the suspend back to the controller to finish. Your windows come back the next time the bench wakes.

Response shape

All fremforge API errors are RFC 9457 problem+json:

{
  "type": "https://docs.frem.sh/reference/api/errors/bench-in-error",
  "title": "Conflict",
  "status": 409,
  "detail": "..."
}

Branch on type, not on title or detail - those are human-readable and may be reworded.

Bench cap reached Bench not found