Skip to content

Errors

Every refusal has the same JSON body:

{"error": "Not a member of this project", "code": "PERMISSION_DENIED", "message": "Not a member of this project",
"remedy": "Use a credential whose scope, kind and project reach this operation, or ask a project administrator for access.",
"docs": "/docs/reference/errors/#permission_denied", "request_id": "req_4f0c..."}

code is stable; message (also sent as error, for older clients) is for people. request_id equals the X-Request-Id header that every response carries; quote it when you report a failure. docs links to the code’s heading below. A 503 with busy and a 429 with RATE_LIMITED carry Retry-After.

A refused machine credential also carries stage (no-credential, malformed-credential, credential-refused, access-denied); its remedy and docs are then the stage’s own, under “Refused credentials (stage)”. The status and code are the same as without it. An unknown, expired or removed key gets one answer.

Generated from the Platform’s error policy by tools/errors_page.py; do not edit by hand.

Correct the request: compare its fields with the operation’s schema in /api/v1/openapi.json and send it again.

Sign in again, or send a current project access key as Authorization: Bearer.

Use a credential whose scope, kind and project reach this operation, or ask a project administrator for access.

Send the bearer credential alone: no browser cookie and no Origin header.

Send a current agent key as Authorization: Bearer, or sign in (RFC 6750).

Check the project, operation and identifiers; list them again to find current ones.

Use the HTTP method the operation documents: POST for operations, GET for resources.

Send a smaller request, within the limit the message names.

Retry later; if it persists, ask the deployment’s operator to check the service.

Retry after the number of seconds in Retry-After.

Wait for the number of seconds in Retry-After, then retry.

Retry once; if it fails again, report the request id to the deployment’s operator.

Report the request id to the deployment’s operator; the request was not completed.

The payload store cannot be reached: retry later.

The script runner is not available on this deployment: retry later or ask its operator.

The embedding model is not available: retry later, or search by words.

Nothing arrived in the Authorization header. Check the application’s authentication setting: the value is Bearer, one space and the key, with no line break after it. Run ophiolite doctor —online to check the key itself.

Send Authorization: Bearer, one space and the key exactly as copied with its Copy button: no other scheme, no space or line break inside it.

This key is unknown, expired or removed. Create a new key on the account page (Project access keys) and put it in the application.

The key was accepted but does not reach this. Use a key for this project with the scope the operation needs, or ask a project administrator for access.

Ask the source’s owner for access, or reconnect with a credential that can read it.

The upstream item was deleted: select another one.

This source was detached from the project: ask a project administrator to choose Resume checks.

The upstream item is gone: select another one, or reconnect the source.

Review the source’s mapping or selection in the Workspace, then try again.

The upstream system cannot be reached: retry later, or ask its administrator.

The source is still being prepared: retry after it is ready.

The requested upstream revision is no longer available: fetch the current one.

Review the source with the database sign-in you use now, or sign in as the person who reviewed it.

The cursor is older than the retained history: start again from changes/head.

Ask a project administrator for edit access; the unfinished upload was discarded.

Read the reason the answer names (reason): a policy says only how long a proposal waits, 1 to 168 hours.

The agent’s scopes, budget or expiry do not allow this: ask its owner to widen them, or act yourself.

AI-use permissions changed: read them again and repeat the grant.

Open the version the answer names (version), or change the settings before publishing again.

Who can see the new version changed: read the people the answer names (recipients) and confirm again.

This is a copy of a project owned elsewhere: make changes on the owning deployment.

This project moved to another deployment: make changes there.

The agent’s budget for today is spent: retry tomorrow, or ask its owner to raise it.

Reduce the request (fewer rows, a smaller area or file) to fit the stated limit.

Correct the one field the answer names (field) and send the check again; nothing was stored.

Read the reason the answer names (reason): ask for the current question again and let the person you act for answer it.

Show the question and the choices to the person you act for; they answer it themselves. Nothing was done.

Another request is adding this file: read the upload’s report and continue with the next file.

This command id belongs to another request: use a new command id.

Send a new command_id: this one was already used for a different command.

Send the expected generation (or revision) you read, so the change applies only to that state.

Read the reason the answer names (reason) and its sentence; what was added from the file stays. Change what it names and declare again with a new command id.

Read the first page again: the cursor belongs to another caller, request or view.

Try it on your own computer, or ask for a trial.

Read the reason the answer names (reason): send dry_run as true on the request itself, never inside a proposal.

A dry run of this operation is not offered on this deployment yet: send the request without dry_run, or ask its operator.

Ask a project administrator for edit access to this project.

The well or wellbore changed or already exists: read it again and repeat the change.

Open the project again; the well or wellbore was removed and its history stays in Activity.

Choose another well, or answer Not this one.

Start the upload again; unfinished uploads are removed after the time the message names.

Start the upload again with the same file; nothing was saved.

Send a file within the size the message names, or ask the deployment’s operator to raise the limit.

The result group changed: read it again and repeat the change.

Send at most the first 65,536 bytes of the file as its head.

Choose inputs whose scientific context (CRS, units, datum) matches the operation.

The stored content does not match what was expected: read it again before changing it.

Use a relationship the registry allows for these subject and object kinds (GET /api/v1/contracts).

Open the list of wells again to see the wells already created.

Open the list of wells again and answer it as it is now.

Open the list of wells again.

Read the reason the answer names (reason): send the mapping without evidence, answer the import’s questions first, or let the person you act for do what is not open to assistants. Nothing was read or added.

Correct the well name in the file and add the file again.

Read the whole original file instead; nothing was read.

Wait for other uploads to finish or remove files you no longer need, or ask the operator for more room.

Correct the file as the message describes and upload it again; nothing was saved.

This deployment does not accept this kind of seismic cube yet; send the cube as 4-byte floats (segy/1) with a trace at every position.

Check the identifiers; list the assets or entities again to find current ones.

Ask the person who created these wells, or a project administrator, to remove them.

Open the list again for the files you want, and answer that list.

Read the reason the answer names (reason) and its sentence; nothing was stored. Change what it names and send again with a new command id.

Send the same part again; if it arrives damaged twice, check the connection and continue the upload.

Propose the exact request with agents/propose, have it approved, and send X-Ophiolite-Plan naming the plan.

Read the reason the answer names (reason) and its sentence; nothing was stored or sent.

Read the reason the answer names (reason) and its sentence; the run was not kept. Change what it names and report again with a new command id.

An input came from a release with a fixed audience: choose people instead of the whole project.

Share the input the answer names (input) with the whole project first, or choose people instead.

Say why the change is narrower (reason), then send it again.

You can no longer read every version this command named: read the survey instead of replaying the command.

Recipients changed since you read them: read the current grants and repeat the change.

A newer revision exists: read the current revision and repeat the change against it.

The rights changed since you read them: read them again and repeat the change with their current generation.

Ask the project administrator to renew the rights to use this data.

Correct the data so the rule the message names passes, or ask a project administrator to show failed rules instead of refusing the file.

Leave out the stopped upload or import the message names, or add its files again in a new one.

This folder upload was stopped: choose the files again in a new upload.

Wait until the upload or import the message names has finished, then ask again.

Choose between 1 and 50 finished folder uploads or table imports and ask again.

The source selection changed: read it again and repeat the change.

Continue the file with the upload its folder upload began for it; read the report for its upload id.

The project setting changed since you read it: read it again and repeat the change.

Choose which of the wells it means.

The review stage changed: read it again and repeat the transition.

The survey changed since you read it: read its current revision and repeat the command against it.

Another survey already holds this identity: read that survey, or choose another key.

Correct the field the refusal names (reason, field) and send the command again; nothing was changed.

Ask the survey’s owner or a project administrator to make the change.

Remove relations, or split the survey, to stay within the relation limits the message names.

Check the survey id; list the project’s surveys again to find the ones you may read.

The survey was withdrawn: it can no longer be read or changed; create a new survey if one is needed.

Link fewer names at once, or split the file and add the parts separately.

Finish or stop an earlier folder upload in this project first.

Create at most 500 wells at once, then open the list again.

Report the tool run first, then publish its result as a step of that run.

Start the folder upload again; this deployment does not know that upload, or it is not yours.

Start the upload again; this deployment does not know that upload.

Use a public HTTPS address; private, loopback and link-local addresses are refused.

Choose one of the supported CRSs the message lists.

Read the reason and field the answer names (reason, field) and its sentence; nothing was stored. Read the verdicts again, change what it names and send again with a new command id.

The webhook changed: read it again and repeat the change with its current generation.

Open the list of wells again to link to the well that was added.

Keep the wells: one was given a registry number or shared since it was created.

Remove or move the later data the message names first, or keep the wells; an administrator sees what you cannot.

Read the reason the answer names (reason) and its sentence; nothing was read. Change the range it names and ask again.

Read the current state again and repeat the change against it.

The request was cancelled before it finished: send it again.

Retry once; if it fails again, report the request id.

Retry later, with a smaller request if you can.

It already exists: read it instead of creating it again.

Retry later, or reduce the request.

Read the current state and bring it to what the operation needs first.

Read the current state again and repeat the change against it.

Use values inside the range the message names.

This deployment does not offer the operation.

Report the request id to the deployment’s operator.