Test with Execute and pinned data

Execute workflow

Execute workflow, at the bottom of the canvas, runs the whole draft now. If the workflow has more than one trigger, pick which one to start from. Each node shows its status as it runs, and each line shows how many items passed along it.

Next to the button, a chip estimates how many credits a run will use. Check it before you run a workflow with Generate nodes.

Execute step

You do not have to run everything to test one node. Open a node and click Execute step, or use the play button that appears when you hover a node. Pinnora runs that node and any earlier nodes it depends on. If an earlier node already ran and nothing above it changed, Pinnora reuses that result instead of running it again.

A node with a yellow warning has changed since its last run. Its output may be out of date. Run it again to refresh it.

Test runs are real

A test run does real work. Generate nodes make real creatives and use credits. Publish now posts. Broadcast sends. Before you test a workflow that reaches the outside world, decide what you want to happen.

You have two ways to hold a node back:

• Deactivate it. Press D on a selected node. A deactivated node passes its input straight through and does nothing.
• Pin data on it. See below.

Pinned data

Pinning saves a node's output and reuses it in every test run. The node does not run again while it is pinned. A banner in the Output pane says the data is pinned for test runs, with a button to unpin.

Pinning is useful in three cases:

• Slow steps. Pin a video render once, then test the steps after it in seconds.
• Steps that cost credits. Pin a Generate node so you are not charged each time you test the caption step after it.
• Steps that act. Pin a node that posts or sends, so your tests do not post or send again.

You can also edit pinned data by hand, which is a quick way to test an edge case like an empty title.

Pinned data only affects test runs. When the workflow is live, every node runs for real.

Where test runs go

Every test run is saved in the Executions tab with a Test badge. You can open it later and see what each node did.