{% extends "_layout.html" %} {% set title = "Not ready yet" %} {% set status = "409 Conflict" %} {% set description = "The output exists in the contract but not yet in storage. Retry." %} {% block main %}

An output the contract promises is not available yet, and is still expected — the log of a node that has not started, or of a whole job none of whose nodes has; an artifact whose provenance is still pending; or a node archive with a member that is. It is transient. It is never a staging failure: a job the server could not get ready ends failed, staging-failed.

What to do

  1. Wait for Retry-After and ask again.

Formerly logs-not-ready. It is one type now, with artifact_kind naming what is not ready.

The body

{
  "type":     "https://sc.example.com/server-errors/not-ready",
  "title":    "Not ready yet",
  "status":   409,
  "detail":   "...",
  "instance": "/v1/jobs/01J9...",
  "artifact_kind": "logs",  // REQUIRED on this type
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
Member
artifact_kindREQUIRED The kind of output that is not ready yet: logs on …/logs, the artifact’s own kind on …/artifacts/{artifact_id}.
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

GET /v1/jobs/{id}/logs For a node, or a whole job, that has not started.
GET /v1/jobs/{id}/artifacts/{artifact_id} An artifact whose provenance is still pending — it will be fetchable once it is described — or a node archive with a pending member. A pending member is reported only when nothing permanent stands in the way: a member withheld, or one you lack a resource for, is refused for that instead.
{% include "_help.html" %}

What this is not

feature-unsupported is permanent: the deployment does not have it at all. Retrying this one is right; retrying that one is not.

not-found is a thing that is not there for you, not one that is on its way.

{% endblock %}