Refusals #

View this page as Markdown

This page lists every refusal a Turn Zero Track (tzTrack) tool call or REST API call meets, with its status, its cause, and its remedy. A refused call changes nothing: correct what the remedy says, then repeat it.

The server at https://tztrack.ai/mcp answers the working tools itself, so their refusals come from it. The REST API answers its acts the same way, with the same refusals. share, create_issue_space, and feedback are carried to Turn Zero Cloud under the same sign-in, so theirs come from Turn Zero Cloud. Each refusal names itself in the answer's error member.

At the server #

Refusal Status Cause Remedy
credential_required 401 The call carried no sign-in. Sign in through your tool. In Claude or ChatGPT, connect tzTrack again in the app's connector settings. In Claude Code, run /mcp and choose tztrack. In Codex, run codex mcp login tztrack. A REST API call sends its tzTrack token in the authorization header (REST API).
credential_refused 401 The server does not accept your sign-in: it expired or was revoked, your account's access to tzTrack ended, or your account is suspended. The detail says which. Sign in again through your tool, as above. A REST API caller sends a fresh tzTrack token (REST API). A suspended account works again only once Turn Zero restores it.
space_mismatch 403 The space named is not one your account owns or is a member of, or it does not exist. Name a space your account owns or is a member of, or leave space out to use your account's one space.
space_closed 403 In a space shared with you, the owner no longer holds tzTrack, so the space is closed to its members until the owner signs in again. Ask the owner to sign in again. Your calls work once the owner's next call is made.
grant_required 403 In a space shared with you, the call is past the level its owner gave you: report files and reads, contribute works issues too, owner also closes and reopens them. The detail names your level and the level the act takes, lowest first file, report, contribute, record, and owner. Stay within your level, or ask the owner for a higher one with share.
invalid_request 400 Input is malformed or missing, or names something the server does not take. The detail names the member. Correct the member the detail names, then repeat the call.
invalid_request, naming create_issue_space 400 Your account holds no space yet, so there is nowhere to work. Call create_issue_space once, then repeat the call.
invalid_request, naming several spaces 400 Your account owns or is a member of more than one space, and the call named none. Pass space with the id of the one to work in.
issue_not_found 404 No issue of the space holds that number. Check the number with find.
report_not_found 404 A REST API follow, or a submit naming amends or withdraws, named a report the space does not hold, or one that is not yours. Read the issue, whose reports list their numbers, and name one of yours.
build_not_found 404 A REST API ship, or a settle naming fixed_in, named a build no deploy recorded. Record the build with deploy first, then repeat the call.
attachment_not_found 404 A REST API attachment named an image the space does not hold. Read the issue, whose reports and comments list each image's id.
attachment_space_full 409 The images would take the space past its storage for images. Send fewer or smaller images, or file the point without them.
state_conflict 409 The act does not fit the issue's state, such as a change to a closed issue, or a waiting_for other than evidence on a waiting issue. Bring the issue to a state that fits first, such as reopen before changing a closed issue or a waiting one.
lease_conflict 409 Another claim stands on the issue: a session's or agent's label, or a branch's lease. Leave the issue to that claim, which is given back when its work ends. A label claim an ended session left may be given back with give_back and a reason; a branch's lease only by the session that holds its secret.
relation_refused 409 The server refused the link between two issues. Correct the link the detail names.
body_too_large 413 The call's text is too long. Shorten the text, or split it into comments.
rate_limited 429 Too many calls within the minute: into the space, from your account on calls that work no space, or from one address with no valid sign-in. The detail names which. Wait for the minute to turn, then repeat the call.
platform_unreachable 503 share, create_issue_space, or feedback could not reach Turn Zero Cloud, so nothing was done there. Repeat the call after a short wait.

From Turn Zero Cloud #

share, create_issue_space, and feedback answer these refusals as Turn Zero Cloud gives them.

Refusal Status Cause Remedy
invalid_request 400 Input is malformed or missing. The detail names the member. Correct the member the detail names, then repeat the call.
space_not_owned 403 share named a space your account does not own. Only the owner shares a space. Name a space your account owns, or ask its owner to share it.
blueprint_required 403 Your account does not hold tzTrack. The name is kept: read it as "this account does not hold the product". Sign in with the Turn Zero account that holds tzTrack.
no_such_account 404 share named an email address no Turn Zero account signs in with, so nothing was kept. Check the address, or have the person create an account first, then add them again.
space_creation_ceiling 403 create_issue_space would take your account past fifty spaces of its own, so nothing was made. Work in a space your account already holds. No act deletes a space, so the limit stands. A repeat naming a space your account already holds returns that space.
feedback_rate_limited 429 A per-minute bound passed: your account's feedback or your account's space creations. The detail names which. Wait for the minute to turn, then repeat the call.
issue_service_unreachable 503 Turn Zero Cloud could not reach the issue service. Repeat the call after a short wait.