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.
Requests and credentials
Section titled “Requests and credentials”INVALID_ARGUMENT
Section titled “INVALID_ARGUMENT”Correct the request: compare its fields with the operation’s schema in /api/v1/openapi.json and send it again.
UNAUTHENTICATED
Section titled “UNAUTHENTICATED”Sign in again, or send a current project access key as Authorization: Bearer.
PERMISSION_DENIED
Section titled “PERMISSION_DENIED”Use a credential whose scope, kind and project reach this operation, or ask a project administrator for access.
MACHINE_AUTH_REQUIRED
Section titled “MACHINE_AUTH_REQUIRED”Send the bearer credential alone: no browser cookie and no Origin header.
invalid_token
Section titled “invalid_token”Send a current agent key as Authorization: Bearer, or sign in (RFC 6750).
NOT_FOUND
Section titled “NOT_FOUND”Check the project, operation and identifiers; list them again to find current ones.
METHOD_NOT_ALLOWED
Section titled “METHOD_NOT_ALLOWED”Use the HTTP method the operation documents: POST for operations, GET for resources.
PAYLOAD_TOO_LARGE
Section titled “PAYLOAD_TOO_LARGE”Send a smaller request, within the limit the message names.
Service state
Section titled “Service state”UNAVAILABLE
Section titled “UNAVAILABLE”Retry later; if it persists, ask the deployment’s operator to check the service.
Retry after the number of seconds in Retry-After.
RATE_LIMITED
Section titled “RATE_LIMITED”Wait for the number of seconds in Retry-After, then retry.
REQUEST_FAILED
Section titled “REQUEST_FAILED”Retry once; if it fails again, report the request id to the deployment’s operator.
INTERNAL
Section titled “INTERNAL”Report the request id to the deployment’s operator; the request was not completed.
store-unavailable
Section titled “store-unavailable”The payload store cannot be reached: retry later.
runner-unavailable
Section titled “runner-unavailable”The script runner is not available on this deployment: retry later or ask its operator.
embedding-unavailable
Section titled “embedding-unavailable”The embedding model is not available: retry later, or search by words.
Refused credentials (stage)
Section titled “Refused credentials (stage)”stage-no-credential
Section titled “stage-no-credential”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.
stage-malformed-credential
Section titled “stage-malformed-credential”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.
stage-credential-refused
Section titled “stage-credential-refused”This key is unknown, expired or removed. Create a new key on the account page (Project access keys) and put it in the application.
stage-access-denied
Section titled “stage-access-denied”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.
Upstream sources
Section titled “Upstream sources”SOURCE_ACCESS_DENIED
Section titled “SOURCE_ACCESS_DENIED”Ask the source’s owner for access, or reconnect with a credential that can read it.
SOURCE_DELETED
Section titled “SOURCE_DELETED”The upstream item was deleted: select another one.
SOURCE_DETACHED
Section titled “SOURCE_DETACHED”This source was detached from the project: ask a project administrator to choose Resume checks.
SOURCE_MISSING
Section titled “SOURCE_MISSING”The upstream item is gone: select another one, or reconnect the source.
SOURCE_NEEDS_REVIEW
Section titled “SOURCE_NEEDS_REVIEW”Review the source’s mapping or selection in the Workspace, then try again.
SOURCE_OFFLINE
Section titled “SOURCE_OFFLINE”The upstream system cannot be reached: retry later, or ask its administrator.
SOURCE_PENDING
Section titled “SOURCE_PENDING”The source is still being prepared: retry after it is ready.
SOURCE_REVISION_UNAVAILABLE
Section titled “SOURCE_REVISION_UNAVAILABLE”The requested upstream revision is no longer available: fetch the current one.
SOURCE_SIGN_IN_ROWS_DIFFER
Section titled “SOURCE_SIGN_IN_ROWS_DIFFER”Review the source with the database sign-in you use now, or sign in as the person who reviewed it.
Data and collaboration
Section titled “Data and collaboration”CURSOR_EXPIRED
Section titled “CURSOR_EXPIRED”The cursor is older than the retained history: start again from changes/head.
access-lost
Section titled “access-lost”Ask a project administrator for edit access; the unfinished upload was discarded.
agent-policy-refused
Section titled “agent-policy-refused”Read the reason the answer names (reason): a policy says only how long a proposal waits, 1 to 168 hours.
agent-refused
Section titled “agent-refused”The agent’s scopes, budget or expiry do not allow this: ask its owner to widen them, or act yourself.
ai-use-changed
Section titled “ai-use-changed”AI-use permissions changed: read them again and repeat the grant.
already-a-version
Section titled “already-a-version”Open the version the answer names (version), or change the settings before publishing again.
audience-changed
Section titled “audience-changed”Who can see the new version changed: read the people the answer names (recipients) and confirm again.
authority-copy
Section titled “authority-copy”This is a copy of a project owned elsewhere: make changes on the owning deployment.
authority-transferred
Section titled “authority-transferred”This project moved to another deployment: make changes there.
budget-exhausted
Section titled “budget-exhausted”The agent’s budget for today is spent: retry tomorrow, or ask its owner to raise it.
capacity-exceeded
Section titled “capacity-exceeded”Reduce the request (fewer rows, a smaller area or file) to fit the stated limit.
check-refused
Section titled “check-refused”Correct the one field the answer names (field) and send the check again; nothing was stored.
choice-refused
Section titled “choice-refused”Read the reason the answer names (reason): ask for the current question again and let the person you act for answer it.
choice-required
Section titled “choice-required”Show the question and the choices to the person you act for; they answer it themselves. Nothing was done.
claimed
Section titled “claimed”Another request is adding this file: read the upload’s report and continue with the next file.
command-owned
Section titled “command-owned”This command id belongs to another request: use a new command id.
command-reused
Section titled “command-reused”Send a new command_id: this one was already used for a different command.
condition-required
Section titled “condition-required”Send the expected generation (or revision) you read, so the change applies only to that state.
conversion-refused
Section titled “conversion-refused”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.
cursor-stale
Section titled “cursor-stale”Read the first page again: the cursor belongs to another caller, request or view.
demonstration-read-only
Section titled “demonstration-read-only”Try it on your own computer, or ask for a trial.
dry-run-refused
Section titled “dry-run-refused”Read the reason the answer names (reason): send dry_run as true on the request itself, never inside a proposal.
dry-run-unavailable
Section titled “dry-run-unavailable”A dry run of this operation is not offered on this deployment yet: send the request without dry_run, or ask its operator.
edit-required
Section titled “edit-required”Ask a project administrator for edit access to this project.
entity-conflict
Section titled “entity-conflict”The well or wellbore changed or already exists: read it again and repeat the change.
entity-removed
Section titled “entity-removed”Open the project again; the well or wellbore was removed and its history stays in Activity.
entity-unavailable
Section titled “entity-unavailable”Choose another well, or answer Not this one.
expired
Section titled “expired”Start the upload again; unfinished uploads are removed after the time the message names.
file-mismatch
Section titled “file-mismatch”Start the upload again with the same file; nothing was saved.
file-too-large
Section titled “file-too-large”Send a file within the size the message names, or ask the deployment’s operator to raise the limit.
group-changed
Section titled “group-changed”The result group changed: read it again and repeat the change.
head-too-large
Section titled “head-too-large”Send at most the first 65,536 bytes of the file as its head.
incompatible-context
Section titled “incompatible-context”Choose inputs whose scientific context (CRS, units, datum) matches the operation.
integrity-conflict
Section titled “integrity-conflict”The stored content does not match what was expected: read it again before changing it.
invalid-relationship
Section titled “invalid-relationship”Use a relationship the registry allows for these subject and object kinds (GET /api/v1/contracts).
list-accepted
Section titled “list-accepted”Open the list of wells again to see the wells already created.
list-changed
Section titled “list-changed”Open the list of wells again and answer it as it is now.
list-removed
Section titled “list-removed”Open the list of wells again.
mapping-refused
Section titled “mapping-refused”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.
name-unusable
Section titled “name-unusable”Correct the well name in the file and add the file again.
native-form
Section titled “native-form”Read the whole original file instead; nothing was read.
no-room
Section titled “no-room”Wait for other uploads to finish or remove files you no longer need, or ask the operator for more room.
not-a-volume
Section titled “not-a-volume”Correct the file as the message describes and upload it again; nothing was saved.
not-admitted
Section titled “not-admitted”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.
not-found
Section titled “not-found”Check the identifiers; list the assets or entities again to find current ones.
not-yours
Section titled “not-yours”Ask the person who created these wells, or a project administrator, to remove them.
other-runs
Section titled “other-runs”Open the list again for the files you want, and answer that list.
outcome-refused
Section titled “outcome-refused”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.
part-corrupt
Section titled “part-corrupt”Send the same part again; if it arrives damaged twice, check the connection and continue the upload.
plan-required
Section titled “plan-required”Propose the exact request with agents/propose, have it approved, and send X-Ophiolite-Plan naming the plan.
procedure-refused
Section titled “procedure-refused”Read the reason the answer names (reason) and its sentence; nothing was stored or sent.
procedure-run-refused
Section titled “procedure-run-refused”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.
project-input-fixed-audience
Section titled “project-input-fixed-audience”An input came from a release with a fixed audience: choose people instead of the whole project.
project-input-not-shared
Section titled “project-input-not-shared”Share the input the answer names (input) with the whole project first, or choose people instead.
reason-required
Section titled “reason-required”Say why the change is narrower (reason), then send it again.
receipt-not-readable
Section titled “receipt-not-readable”You can no longer read every version this command named: read the survey instead of replaying the command.
recipients-changed
Section titled “recipients-changed”Recipients changed since you read them: read the current grants and repeat the change.
revision-conflict
Section titled “revision-conflict”A newer revision exists: read the current revision and repeat the change against it.
rights-conflict
Section titled “rights-conflict”The rights changed since you read them: read them again and repeat the change with their current generation.
rights-ended
Section titled “rights-ended”Ask the project administrator to renew the rights to use this data.
rule-refused
Section titled “rule-refused”Correct the data so the rule the message names passes, or ask a project administrator to show failed rules instead of refusing the file.
run-cancelled
Section titled “run-cancelled”Leave out the stopped upload or import the message names, or add its files again in a new one.
run-ended
Section titled “run-ended”This folder upload was stopped: choose the files again in a new upload.
run-not-finished
Section titled “run-not-finished”Wait until the upload or import the message names has finished, then ask again.
runs-count
Section titled “runs-count”Choose between 1 and 50 finished folder uploads or table imports and ask again.
selection-changed
Section titled “selection-changed”The source selection changed: read it again and repeat the change.
session-mismatch
Section titled “session-mismatch”Continue the file with the upload its folder upload began for it; read the report for its upload id.
settings-changed
Section titled “settings-changed”The project setting changed since you read it: read it again and repeat the change.
several-match
Section titled “several-match”Choose which of the wells it means.
stage-changed
Section titled “stage-changed”The review stage changed: read it again and repeat the transition.
survey-changed
Section titled “survey-changed”The survey changed since you read it: read its current revision and repeat the command against it.
survey-identity-taken
Section titled “survey-identity-taken”Another survey already holds this identity: read that survey, or choose another key.
survey-invalid
Section titled “survey-invalid”Correct the field the refusal names (reason, field) and send the command again; nothing was changed.
survey-not-editable
Section titled “survey-not-editable”Ask the survey’s owner or a project administrator to make the change.
survey-relation-limit
Section titled “survey-relation-limit”Remove relations, or split the survey, to stay within the relation limits the message names.
survey-unavailable
Section titled “survey-unavailable”Check the survey id; list the project’s surveys again to find the ones you may read.
survey-withdrawn
Section titled “survey-withdrawn”The survey was withdrawn: it can no longer be read or changed; create a new survey if one is needed.
too-many-names
Section titled “too-many-names”Link fewer names at once, or split the file and add the parts separately.
too-many-runs
Section titled “too-many-runs”Finish or stop an earlier folder upload in this project first.
too-many-wells
Section titled “too-many-wells”Create at most 500 wells at once, then open the list again.
tool-run-refused
Section titled “tool-run-refused”Report the tool run first, then publish its result as a step of that run.
unknown-run
Section titled “unknown-run”Start the folder upload again; this deployment does not know that upload, or it is not yours.
unknown-upload
Section titled “unknown-upload”Start the upload again; this deployment does not know that upload.
unsafe-destination
Section titled “unsafe-destination”Use a public HTTPS address; private, loopback and link-local addresses are refused.
unsupported-crs
Section titled “unsupported-crs”Choose one of the supported CRSs the message lists.
verdict-refused
Section titled “verdict-refused”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.
webhook-changed
Section titled “webhook-changed”The webhook changed: read it again and repeat the change with its current generation.
well-appeared
Section titled “well-appeared”Open the list of wells again to link to the well that was added.
wells-changed
Section titled “wells-changed”Keep the wells: one was given a registry number or shared since it was created.
wells-referred
Section titled “wells-referred”Remove or move the later data the message names first, or keep the wells; an administrator sees what you cannot.
window-refused
Section titled “window-refused”Read the reason the answer names (reason) and its sentence; nothing was read. Change the range it names and ask again.
Native service (gRPC status names)
Section titled “Native service (gRPC status names)”CONFLICT
Section titled “CONFLICT”Read the current state again and repeat the change against it.
CANCELLED
Section titled “CANCELLED”The request was cancelled before it finished: send it again.
UNKNOWN
Section titled “UNKNOWN”Retry once; if it fails again, report the request id.
DEADLINE_EXCEEDED
Section titled “DEADLINE_EXCEEDED”Retry later, with a smaller request if you can.
ALREADY_EXISTS
Section titled “ALREADY_EXISTS”It already exists: read it instead of creating it again.
RESOURCE_EXHAUSTED
Section titled “RESOURCE_EXHAUSTED”Retry later, or reduce the request.
FAILED_PRECONDITION
Section titled “FAILED_PRECONDITION”Read the current state and bring it to what the operation needs first.
ABORTED
Section titled “ABORTED”Read the current state again and repeat the change against it.
OUT_OF_RANGE
Section titled “OUT_OF_RANGE”Use values inside the range the message names.
UNIMPLEMENTED
Section titled “UNIMPLEMENTED”This deployment does not offer the operation.
DATA_LOSS
Section titled “DATA_LOSS”Report the request id to the deployment’s operator.
