> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-graphql-api/products/console/errors.md). # Console errors How the Console operations use the shared error codes. The Console operations return errors in the shared Navixy GraphQL API format, using the same codes as every other product. Consult this page if you call the `console` operations for your workspace: the queries that list your organizations and workspaces, and the operations that read and change the products of a workspace. It covers where Console differs from the other products in the use of shared codes. For the response structure, the full list of codes, and general scenarios, see [Error handling](/docs/navixy-graphql-api/error-handling.md). A `console` request can be refused twice. The API checks your token and your arguments first. Then Navixy Console decides what you may see and do, and the API relays its answer. The `dependency` field says which of the two refused. ## Refusals relayed from Navixy Console When Console refuses a request, the API returns the matching shared code and marks the error with `dependency: "console"`. Console's own error code is in `dependencyCode`, and `entityType` names what the request was about. The `message` and `detail` name the operation, such as "Console refused the workspace-product-enable request", and say nothing more, so branch on `dependencyCode`.
Console answersCodedependencyCode on the product operations
400VALIDATION_ERRORPRODUCT_UNKNOWN: no product has the code. PRODUCT_NOT_TOGGLABLE: the product can't be turned on or off.
401, 403PERMISSION_DENIEDWORKSPACE_PRODUCTS_FORBIDDEN, WORKSPACE_OPERATION_FORBIDDEN, PRODUCT_CATALOG_FORBIDDEN: your roles lack the Console administration feature or the action on the workspace. On members, your roles lack the Console administration feature.
404NOT_FOUNDWORKSPACE_NOT_FOUND: the workspace doesn't belong to your organization. See Missing workspaces and operations.
409CONFLICTPRODUCT_NOT_COVERED: no active subscription covers the product. PRODUCT_MANAGED_BY_PLAN: the plan requires the product. PRODUCT_NOT_ENABLED: nothing to disable. WORKSPACE_TERMINATING: the workspace is being deleted.
Anything else or no answerSERVICE_UNAVAILABLENone.
Enabling a product that no active subscription of your workspace covers returns this error: ```json { "errors": [{ "message": "Console refused the workspace-product-enable request", "path": ["console", "workspaceProductEnable"], "extensions": { "type": "https://api.navixy.com/errors/conflict", "title": "Concurrent Modification Conflict", "status": 409, "detail": "Console refused the workspace-product-enable request", "instance": "/graphql", "code": "CONFLICT", "dependency": "console", "dependencyCode": "PRODUCT_NOT_COVERED", "entityType": "ConsoleWorkspaceProduct", "traceId": "0af7651916cd43dd8448eb211c80319c", "timestamp": "2026-09-28T10:45:00Z" } }], "data": { "console": { "workspaceProductEnable": null } } } ``` ### How to handle a refusal from Console Read `dependencyCode` and act on the reason, not on the shared code. A `CONFLICT` from Console is a refusal in the current state of the product or the workspace, not a concurrent change: it has no `expectedVersion`, and sending the same request again fails the same way. For a product that isn't covered, subscribe your workspace to a plan that includes it (see [Choosing a plan and subscribing](/docs/navixy-graphql-api/products/billing/guides/choosing-a-plan-and-subscribing.md)). For a product that the plan requires, there is nothing to do: it stays enabled. For a missing feature or action, ask the Owner of your organization for a role that has them. To learn in advance whether a change would be refused, read `allowedActions` on the product with [workspaceProducts](/docs/navixy-graphql-api/products/console/api-reference/products.md#workspaceproducts). ## Missing workspaces and operations The organization and workspace lists cover every organization you belong to, whichever one your token names, but the product operations and `members` act only in the organization named by your token. A product operation on a workspace of another organization returns `NOT_FOUND` with `dependency: "console"` and `entityType: "ConsoleWorkspace"`, not `PERMISSION_DENIED`. Console doesn't say whether the workspace exists. [workspaceOperation](/docs/navixy-graphql-api/products/console/api-reference/products.md#workspaceoperation) is the exception. For an operation ID that Console doesn't know in your organization, it returns `null`, with no entry in `errors`. A role without the `view` action on the workspace of the operation gets `PERMISSION_DENIED` instead. The queries that list your organizations and workspaces never return `NOT_FOUND`. An `organizationId` that names no organization you belong to returns an empty page. `members` returns `NOT_FOUND` with `entityType: "ConsoleOrganization"` when Console doesn't know the organization named by your token. ## Errors before Console is called The API checks your token and your arguments first. These errors have no `dependency` field.
CodeWhen it occursHow to resolve
PERMISSION_DENIEDThe token has no organization_id claim or no workspace_id claim. detail names the missing claim. The Console operations don't fall back to your memberships.Request a token issued for the organization and the workspace. See Access token claims.
VALIDATION_ERRORworkspaceId isn't a workspace ID of this deployment, productId isn't a product ID, the organizationId of accessibleWorkspaces isn't an organization ID of this deployment, or the id of workspaceOperation isn't an operation ID of this deployment. An ID issued in another Navixy region or deployment counts as not valid. field names the argument, for example input.productId or organizationId.Send each ID as the API returned it: the workspace ID from accessibleWorkspaces, the organization ID from accessibleOrganizations, the productId from workspaceProducts, and the operation ID from workspaceProductEnable or workspaceProductDisable.
VALIDATION_ERRORproductCode isn't a valid code. The API refuses the whole request before it runs any field, so the error has no field.Send the code as workspaceProducts returned it.
VALIDATION_ERRORThe paging arguments break Console's rules: first with last or before, last with after, last without before, before without last, or a page size outside 1 to 100. On members, a cursor that isn't one the query returned.Page forward with first and after, backward with last and before. See How these connections paginate.
RATE_LIMITEDYou sent more requests than your rate limit allows.Wait, then retry. See Request rate.
A request whose token names no organization returns this error on every `console` field it selects: ```json { "errors": [{ "message": "the token carries no 'organization_id' claim", "path": ["console", "workspaceProducts"], "extensions": { "type": "https://api.navixy.com/errors/forbidden", "title": "Permission Denied", "status": 403, "detail": "the token carries no 'organization_id' claim", "instance": "/graphql", "code": "PERMISSION_DENIED", "traceId": "0af7651916cd43dd8448eb211c80319c", "timestamp": "2026-09-28T10:45:00Z" } }], "data": null } ``` ### How to handle a missing claim Request a token issued for the organization and the workspace, and send it on every `console` request. A token that works for Business Data Repository can still be refused here: Business Data Repository reads only the `workspace_id` claim and falls back to your single membership, and the Console operations need both claims. ## When Console doesn't respond `SERVICE_UNAVAILABLE` with `dependency: "console"` means that Console didn't respond to the request: Console is unreachable, this deployment has no Console, or Console couldn't reach Billing to read the catalog or the coverage. Retry after a short pause. If the error persists, contact Navixy with its `traceId`. The API returns the same error when Console returns an organization ID or an operation ID that isn't valid. On `workspaceProductEnable` and `workspaceProductDisable`, Console has already accepted the change in this case. Don't send the mutation again: read `workspaceProducts` to follow the state of the product. An organization that you read through `node(id:)` or `nodes(ids:)` is `null` when Console doesn't respond, and the error names its path. The other IDs of the same `nodes(ids:)` call return their results as usual. ## Fields of a Console error A Console error has the standard fields of [Error handling](/docs/navixy-graphql-api/error-handling.md#error-response-structure), with these differences: * `dependency` is `console` on every error that Console answered or failed to answer, and absent on an error that the API raised itself: a missing claim, a malformed argument, or a paging rule. * `dependencyCode` is present when Console returned its own code, and absent on `SERVICE_UNAVAILABLE`. * `entityType` is present on every refusal relayed from Console: `ConsoleWorkspaceProduct` on the product operations, `ConsoleWorkspace` on a workspace that Console doesn't show you, `ConsoleWorkspaceOperation` on an operation, `ConsoleMember` on the members query, and `ConsoleOrganization` when Console doesn't know the organization named by your token. `entityId` is present when Console named the entity. * `field` is present when the API rejected an argument, for example `input.productId`, and when Console rejected a field that maps to an argument. * `expectedVersion` and `currentVersion` are never present. A `CONFLICT` from Console isn't a version check. ## See also * [Error handling](/docs/navixy-graphql-api/error-handling.md): Learn the error structure, every code, and the common scenarios across the API. * [Enabling and disabling a product](/docs/navixy-graphql-api/products/console/guides/enabling-and-disabling-a-product.md): Turn a product on or off and handle the errors of the two mutations. * [Authentication](/docs/navixy-graphql-api/authentication.md): Learn how the token names the organization and the workspace that the Console operations act in. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://navixy.com/docs/navixy-graphql-api/products/console/errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.