Run did not start

A run that fails validation does not enter the generation queue. The node shows the missing or incompatible setting, while a blocked Run button explains its state when you hover over it.

Fix one named problem at a time and press Run again. Rebuilding the node or reconnecting every wire usually makes the cause harder to identify.

The selected model defines what it needs. Some models can generate from text alone. Others require an image, a start frame, or a particular reference type.

• Enter a non-empty prompt when the model requires text.
• Upload the required media or connect a compatible input port.
• Check that the upstream holder contains media rather than an empty placeholder.
• Remove a reference type that the selected model does not accept.

A dash in place of the credit cost means AgentDocks cannot calculate a current price for that model and configuration. The run remains blocked because zero would incorrectly imply that the work is free.

Open the model menu and select another available model. If the problem affects every model, leave the node unchanged and try again later rather than repeatedly pressing Run.

A node is blocked when the available balance is lower than its displayed run estimate. The estimate includes the selected model, supported quality or resolution options, and the number of variants.

Reduce the variant count, choose a lower-cost supported configuration, select another model, or add credits before running again.

A queued or running node is busy until the engine returns an outcome. AgentDocks blocks another press so the same node cannot create two holds and two sets of results by accident.

Check the run tray in the top bar. Select an entry to move to the active node, or use Stop All Runs if the project should stop its current work.

A node that displays In batch belongs to a live batch and cannot be started separately. Its progress appears on the Batch Run node because the batch controls which input is currently being processed.

Wait for the batch to finish or stop the active project run before running that node on its own.

If an authorizing preview disappears and a message appears, the server refused the request before provider work began. This can happen when the project changed, the model configuration became invalid, the request was duplicated, or the current account state no longer permits the run.

Follow the displayed message, refresh the project if its state changed in another tab, and retry only after the cause has been corrected. A refused request is not treated as a failed generation.