{% extends "_layout.html" %} {% set title = "Could not resolve what this flow needs" %} {% set status = "422 Unprocessable Content" %} {% set description = "The server could not decide what the flow needs." %} {% set also_on_a_job = true %} {% block main %}

Reading your manifest while the job staged, the server could not decide which resource it needs — for a PDK, whether a name was intended or the literal none. Nothing was denied: the question could not be asked.

What to do

  1. Read resource_kind.
  2. Name that resource explicitly in your build script and submit again.

The body

{
  "type":     "https://sc.example.com/server-errors/resource-unresolved",
  "title":    "Could not resolve what this flow needs",
  "status":   422,
  "detail":   "...",
  "instance": "/v1/jobs/01J9...",
  "resource_kind": "pdk",  // REQUIRED on this type
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
Member
resource_kindREQUIRED The kind that could not be resolved.
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/{id}/submit By the manifest’s read, while the job stages, after the archive is opened.
{% include "_help.html" %}

What this is not

resource-unavailable is a resource the server identified and does not hold.

entitlement-denied is a resource you may not use.

{% endblock %}