Run stuck or slow

Shimmer

The run has been accepted and is being authorised: credits are being held. This lasts seconds.

Queued

The node is waiting, either for an upstream trigger to finish or for a free slot. Runs on one account share a small number of slots, and a batch works four items at a time.

Running, with a stage label and a timer

The provider has the request. The label says which stage it is in and the timer shows elapsed time. There is no percentage on purpose: generation times vary and a bar would only stick at the end.

Failed, with a reason

The box shows what went wrong, the credits for it are released, and the box is reused by your next run.

Images usually land within a minute. Video is slower by nature: a clip can take anywhere from one to fifteen minutes depending on the model, the length and the resolution, and the system waits up to about twenty-five minutes for a provider before it gives up and releases the hold. A whole run with one video step is allowed up to an hour before it is treated as lost. If the timer is inside those windows, the run is not stuck; it is working.

1. 1

   Wait out the window for video

   A running video with a moving timer is the normal case. Leave the tab open or come back later; results land whether or not you are watching.
2. 2

   Reload if the page itself looks frozen

   A reload is safe. The editor reconnects to the live run and picks up where it was; nothing is lost and nothing is charged twice.
3. 3

   Check whether another run is active

   A node refuses to start while the project already has an active run, and queued nodes wait for the earlier ones. Let them finish or stop them.
4. 4

   Stop it if you no longer want it

   The top-bar Run control becomes Stop All Runs while anything is active. Steps that have not reached a provider release their credits in full. A step already at a provider is charged unless the provider confirms the cancel; a result that arrives late after a stop is discarded, never charged twice and never added to your project.
5. 5

   Look at the charge afterwards

   Credit usage lists every charge with what it was for. A failed or stopped step that was never delivered appears as a released hold, not a charge.

A box past the windows above with a frozen timer, or a run that fails with no readable reason, is one for support. Serious errors carry an eight-character reference code with a copy button; send that code and a line about what you were doing to support, and the run can be traced exactly.