Know exactly what each image job returns

Connecting a form to ComfyUI raises questions worth settling before you write code: what a visitor may send, what the server keeps, and what a job looks like when it fails. This image job contract writes those answers down so the work is easier to repeat and share.

It defines the request (a nonempty, bounded-length prompt and a client request ID), what the server owns (the graph, checkpoint, node classes and output path), the job record (id, owner, upstream prompt ID, state, timestamps and error code), the states queued, running, complete and failed, and the result as an output ID with an authorized image URL. A timeout is an observation, not a cancellation.

It lists the acceptance cases to test: a valid request, invalid input, provider unavailable, duplicate request, timeout, failed node and cross-user result access. Upstream credentials and ComfyUI network access stay on the server. You need a text editor. Provider accounts, model weights, GPU compute and hosting are not included.