{% extends "_layout.html" %} {% set title = "Not entitled to this resource" %} {% set status = "403 Forbidden" %} {% set description = "Your account is not permitted to use a PDK, tool or library this job asks for." %} {% set also_on_a_job = true %} {% block main %}
Your account holds no grant for something the job asks for, or an artifact derives from — a PDK, a tool, a library or an FPGA device. Only a missing grant is this: an unaccepted agreement is terms-not-accepted. Where a grant through a project lapsed, detail says so.
Retrying will not change this. It is a statement about what your account holds, not about how busy the server is, and the identical request returns the identical answer.
resource_kind and resource to see exactly what was refused.GET /v1/me. The authorized block lists what your account does
hold, keyed by kind (pdks, tools, libraries).POST /v1/auth/browser with
{"resource": "<resource>"} answers the page where you ask for that grant,
or says why there is nothing to ask. A CI session asks for none.
There is no API call that grants it to you.Do not retry on a timer. Nothing about this answer changes with time.
{
"type": "https://sc.example.com/server-errors/entitlement-denied",
"title": "Not entitled to this resource",
"status": 403,
"detail": "The manifest names a PDK this account does not hold.",
"instance": "/v1/jobs/01J9.../submit",
"resource_kind": "pdk", // REQUIRED on this type
"resource": "gf22", // REQUIRED on this type
"trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
| Member | ||
|---|---|---|
resource_kind | REQUIRED | Which kind of thing was refused: pdk, tool,
library, fpga. The kind is a value, never a prefix on the
type. |
resource | REQUIRED | Its name, as the catalogue spells it. |
trace_id | optional | The request’s W3C trace id. Quote it in a support request. |
detail is prose and may be reworded at any time. Branch on type, and
read resource_kind and resource for the specifics — never parse
detail.
POST /v1/jobs |
The descriptor names something you do not hold. |
GET /v1/jobs/{id} |
The enforcing gate, as a rejected job’s error — checked while the job stages, against what the manifest’s read
reports, not against what the descriptor claimed. |
GET /v1/jobs/{id}/artifacts/{artifact_id} |
You do not hold a resource the artifact derives from — and
resource names that resource. A refusal about the object itself is
artifact-not-approved. |
GET /v1/jobs/{id}/logs |
A running node’s live log, when you lack a resource in the job’s set: a live
stream is gated like the archive, and resource names it. |
The submit check is the one that matters. A job can be created successfully and still be refused at submit, because create only saves an upload and submit is where the real manifest is read.
{% include "_help.html" %}insufficient-scope is the same 403
and a different question. This page is your account may not use that thing. That one is
the credential you presented was not minted with permission to make this call — a
narrower token, not a narrower account.
resource-unavailable (422)
means the deployment does not hold the resource and cannot supply it at all. The
question of whether you may use it never arose, and nothing about your account will fix it.
resource-unresolved (422) means
the server could not work out what the flow needs — for a PDK, whether a name or the literal none was intended. Again,
nothing was denied; the question could not be asked.
terms-not-accepted (403) means you
hold the resource but have not accepted a document covering it. That one is fixable by you.
not-found (404) is what a job naming a
project you are not a member of gets — never this, because a 403
would confirm the project exists.