{% extends "_layout.html" %} {% set title = "Too many nodes in this flow" %} {% set status = "403 Forbidden" %} {% set description = "More nodes in one flow than allowed. Send a smaller flow." %} {% block main %}

The flow you submitted has more nodes than this deployment runs in one job. The ceiling is static — it is about the size of the flow, not about what else you have running.

What to do

  1. Compare your flow’s node count with limits.max_job_nodes in GET /v1.
  2. Send a smaller flow: split it, or narrow it with from, to or prune.
  3. Retrying the same flow returns the same answer.

The body

{
  "type":     "https://sc.example.com/server-errors/node-limit-exceeded",
  "title":    "Too many nodes in this flow",
  "status":   403,
  "detail":   "...",
  "instance": "/v1/jobs/01J9...",
  "limit":    "max_job_nodes",  // REQUIRED on this type
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
Member
limitREQUIRED Always max_job_nodes.
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 Counted on the flow the manifest’s read reports, while the job stages.
{% include "_help.html" %}

What this is not

limit-exceeded is a ceiling that refills as your other jobs finish.

{% endblock %}