Troubleshooting and FAQ

Node states

A node failed and everything after it stopped

That is intended. When a node fails, everything downstream is skipped rather than run on missing input. Fix the cause, usually a missing connection on a required port, and run again. Branches that do not depend on the failed node still finish.

The graph refuses to run at all

Check for a loop. A graph has to flow one way, so if connections form a cycle Studio stops and says so instead of running forever. Remove one connection in the loop.

My image came back smaller than I put in

Browser-side operations are capped at 4096 pixels on the long edge. If an image is larger, it is scaled down to fit and the node shows an amber warning saying exactly what happened. Do large-format work outside Studio, or resize deliberately first.

A grade chain looks banded

Utility nodes currently hand results between each other as 8-bit images, so a long chain of colour operations can show steps in smooth gradients. Do the bulk of a correction in one Grade rather than stacking several.

Rotating a crop clipped the corners

Crop / Transform keeps the output the size of the crop, so rotating by anything other than 0 or 180 degrees pushes the corners outside the frame. Crop wider than you need before rotating.

Frame extraction did not land on the frame I wanted

Frame Extractor takes a percentage through the clip rather than a frame number, and lands on whatever frame the browser decoder seeks to. It is not frame accurate.

My saved graph looks different when I open it

Results from browser nodes are not stored; they are recalculated when you run the graph again. Results from AI nodes are stored, so those come back as you left them.

Which nodes re-run on their own?

The 38 browser nodes do, as soon as something upstream of them changes. AI nodes never re-run without you asking, so nothing is generated behind your back. Use Run in the properties panel to execute a single node, or run the whole graph from the menu.

Where do I find every setting for a node?

The node reference has a page for each of the 117 nodes, listing its ports, its settings and their defaults, and where it runs. In Studio, the question mark beside a node's help text opens its page directly.

Still stuck

Use the feedback button in the corner of the app. It carries the context of what you were doing, which makes a report far easier to act on. Studio spans 68 models across 26 providers, and 16 blend modes on the merge node, so being specific about which one misbehaved helps.