EN Team Write Refused 423

Write refused on the hosted Studio: span locked (423)

Français · Type: troubleshooting · Audience: author · Context: hosted Studio · Status: ready · Applies from: 4.2.1

The Studio Server (hosted team Studio) · contract: experimental · verified by CI (support matrix of 4.4.0, 2026-10-23): Postgres, S3 and Keycloak in CI; Chromium and Firefox (job studio-hosted); WebKit on macOS, by hand only · automated checks: jobs studio-hosted, studio-install-smoke; CI plan studioHosted; 3 test files · people's passes: studio-hosted not run (#149), studio-collab not run (#150), studio-preview not run (#166), studio-assets-hosted not run (#167), studio-mcp-remote not run (#196), studio-oidc-generic not run (#197) · known limits: hosted-only

On a team Studio, your save was refused with a 423: another member is editing the same part of the game. Your change is not lost, and nothing was written. This page says how to tell why, and how to get your change in.

Symptom

• In the Studio: a dialog "The room kitchen is held by Léa" (or "The span story is held by…", or "The whole game is held by…"), with "Your change was not applied. Nothing is lost: your draft is kept here, to save when the span is free."
• Through the API, the CLI or the MCP: HTTP 423 with {"error": "room:kitchen is being edited by Léa", "span", "holder", "holderName", "until"}, or "<name> has the whole game for now", or "your lease on <span> ended or was taken again: take it again".

Possible causes

Every file of the game belongs to one span: a room (its code and its layout), a language, the story, the items, the cast, the rules, the voices, the assets, the notes, the map's groupings, the rest. Saving a file takes its span for you for 120 seconds, a lease. Your Studio renews your leases every 30 seconds for as long as it stays open. Then:

1. Another member holds that span's lease: they saved in that room, or took it ahead, and their Studio is still open (or was closed less than two minutes ago). The most common case.
2. A member holds the exclusive lease (*): the whole game is theirs while a job that touches everything runs. Prepare and the cutting of the Assets tab take it for the dev who starts them; an engine upgrade and a Git import take it for the owner who starts them; each gives it back when its job ends. An owner can also take it by hand. Nobody else writes meanwhile.
3. A script's lease ended or was taken over. A client that sends the fences it was given (x-studio-fences) is refused when its lease ran out or an owner took the span over since. Only API clients that choose to send them get this; the Studio and the MCP do not. Your own lease never refuses you, from any of your tabs.

Limit · hosted-only Spans and leases exist on a hosted Studio (the Studio Server) only. The local Studio (npm run studio) has one person and no 423.

Diagnosis

• The dialog names the holder. The Studio's Spans panel lists who holds what, and until when; it follows the server's live events.
• As a member, GET /api/leases gives every lease: span, holderName and until (a time on the server's clock, in milliseconds).
• A span * in the list is an exclusive lease: its holderName is the member whose job (or whose hand) holds it.
• The message "your lease on … ended or was taken again" is cause 3, and only a script sending x-studio-fences sees it.

Fix

1. Wait. Click "Tell me when it is free": the Studio tells you as soon as the lease is given back or runs out. A lease runs out 120 seconds after the holder's Studio stops renewing it (their tab closed, their machine asleep); while their Studio stays open, they keep it, so ask them (next step). Then click "Try again": your draft is sent as it is.

2. Ask. Tell the holder you need that room. When they release the span in their Spans panel, it is free at once.

3. Take it over (owner only). An owner can click "Take over and save (owner)": the span becomes theirs and the change is saved. The previous holder's next write in that span is refused in turn. The takeover is written in the audit log (lease-takeover, with the previous holder). Through the API: POST /api/leases/takeover with {"span": "room:kitchen"}.

4. The exclusive lease. When someone holds the whole game (*) for a job (Prepare, a cutting, an engine upgrade, a Git import), wait for the job to end: the lease is given back with it. An owner who took it by hand gives it back with POST /api/exclusive/release, or it runs out. Taking it by hand (POST /api/exclusive) and releasing it by hand are an owner's; it is granted only when nobody else holds a span.

For cause 3, the script takes the span again (POST /api/leases with {"spans": ["room:kitchen"]}), keeps the new fences it gets, then sends its write again.

Check it is fixed

The save goes through: the Studio shows the new revision, and the Spans panel shows the span as yours. Through the API, the write answers 200 with the revision it made.

Neighbouring cases

• 409, "The file changed since you read it": nobody holds the span, but someone saved the same file after you opened it. That is not a lock; see Write refused on the hosted Studio: stale base revision (409).
• 503 with Retry-After: the instance does not serve writes yet, during a redeploy. Wait a few seconds; the Studio retries.
• A Reality Bridge never answers 423.

---

Edit the source of this page · Report an error