{% extends "_layout.html" %} {% set title = "This server does not hold that resource" %} {% set status = "422 Unprocessable Content" %} {% set description = "The job needs a resource this deployment does not hold and cannot supply, and you could not send it either." %} {% set also_on_a_job = true %} {% block main %}

The job needs a PDK, a library, an FPGA device or a tool that this deployment does not hold and has no way to supply — and it is not one you can send. A resource you can send is never refused this way: the server asks for it instead, in the job’s upload_sources. What is left is a resource marked private, whose copy only the server may supply. A controlled resource you hold no grant for is entitlement-denied, and one found by its contents in your upload is upload-forbidden.

What to do

  1. Read resource to see which, keypath for which of its dataroots, and resource_kind where the deployment names it.
  2. For a private dataroot, ask this deployment’s operator to hold a copy of it under that keypath. Private data is never uploaded, so nothing you send can satisfy it.
  3. Or run against a deployment that holds it.
  4. Retrying the same job returns the same answer.

Also covers what unsatisfiable-request meant, which was retired before the API froze: the two meant this server cannot provide it, with the same members. For software in a version no image holds, see software-unavailable.

The body

{
  "type":     "https://sc.example.com/server-errors/resource-unavailable",
  "title":    "This server does not hold that resource",
  "status":   422,
  "detail":   "...",
  "instance": "/v1/jobs/01J9...",
  "resource": "mypdk",  // REQUIRED on this type
  "keypath":  ["library", "mypdk", "dataroot", "mypdk"],  // where it is a dataroot
  "resource_kind": "pdk",  // where the deployment can name it
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
Member
resourceREQUIRED Its name, or for a dataroot its owner’s: the library’s, or the task’s tool. Names are unique across kinds, so it alone says which resource.
keypathoptional Where it is a dataroot, which one, as sources names it: ["library", name, "dataroot", root], or ["tool", tool, "task", task, "dataroot", root] for a task’s own. Most owners have a dataroot called root, so the owner alone does not say which.
resource_kindoptional pdk, library, fpga or tool, where the deployment can name the kind. One without a catalogue of resources — the reference sc-server is one — leaves it out at create, where a source carries no kind, and names the resource alone. It is never the design.
trace_idoptional 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 the members above for the specifics — never parse detail.

Where it comes from

POST /v1/jobs A private source in the descriptor’s sources that the server does not hold — before the archive uploads, by its name.
POST /v1/jobs/{id}/submit While the job stages, after the archive is opened, against what the manifest’s read reports: a private source the descriptor did not list, with its kind where it is a resource’s.
{% include "_help.html" %}

What this is not

resource-unresolved is the server not being able to work out which resource the flow needs. Here it knows which, and does not have it.

entitlement-denied is a resource the deployment has and you may not use.

software-unavailable is the same answer for images: software no image holds in the version you asked for.

upload-forbidden is files you did upload that you were not allowed to.

{% endblock %}