{% extends "_layout.html" %} {% set title = "Upload of that resource is not allowed" %} {% set status = "422 Unprocessable Content" %} {% set description = "The archive carries restricted material you may not upload. The job is rejected." %} {% set also_on_a_job = true %} {% block main %}

Your upload carries files of a controlled resource — a PDK or library under an agreement — which your account may not upload. The deployment supplies its own copy of controlled resources; it does not accept one from you. The job is rejected and the upload deleted.

What to do

  1. Read detected. attribution: your manifest attributes the file to a controlled resource. content: the file’s bytes match one, whatever the manifest calls it.
  2. Read member, the archive entry that was refused, and resource_kind.
  3. Use the deployment’s copy: reference the resource from its released source instead of a local or editable one, so its files are not uploaded.
  4. If you need to run a modified copy, that is a permission for whoever administers your account.

Only a resource the deployment controls can be refused this way. A deployment with no controlled resources, such as the reference sc-server, never returns it.

The body

{
  "type":     "https://sc.example.com/server-errors/upload-forbidden",
  "title":    "Upload of that resource is not allowed",
  "status":   422,
  "detail":   "...",
  "instance": "/v1/jobs/01J9...",
  "resource_kind": "pdk",  // REQUIRED on this type
  "detected": "content",  // REQUIRED on this type
  "member":   "sc_collected_files/3f9a1c.lef",  // REQUIRED on this type
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
Member
resource_kindREQUIRED pdk, library or fpga.
detectedREQUIRED attribution or content: how the member was found to be controlled. content is found first, by the server’s own reading of the upload before staging starts; attribution once staging’s read of the manifest reports what each member belongs to.
memberREQUIRED The archive entry, bounded. Named only once the archive has passed its safety checks.
resourceOPTIONAL Its name — present only when you hold a grant on it. Otherwise naming it would confirm what the deployment’s catalogue holds.
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

The job, while it stages The job ends rejected and carries this as its error; read it with GET /v1/jobs/{id}. Submit itself accepts the archive on its digest alone.

The order is fixed: content is checked first, then attribution, and both before terms-not-accepted and entitlement-denied on the job’s resources. A caller who holds no grant on the resource therefore gets upload-forbidden with no resource, and never an entitlement-denied that names it.

{% include "_help.html" %}

What this is not

archive-rejected is also raised while the upload is read, and is a safety failure of the archive itself, not a policy about its contents. The fix differs.

resource-unavailable is the opposite case: a resource the server needed and could not get.

{% endblock %}