Executions, debugging, and version history

The Executions tab

Every run is an execution. Open a workflow and switch from Editor to Executions. The list on the left shows each run with its start time, how long it took, and its status: queued, running, waiting, success, error, or canceled. Test runs carry a Test badge.

Replay a run

Click an execution. The canvas on the right shows that run exactly as it happened. Nodes that ran show a tick and an item count. The node that failed shows an error. Open any node to see its input and output from that run, read only.

The Logs panel at the bottom of the editor (press L) lists each node with how long it took and how many credits it used. This is the fastest way to see where time and money went.

Debug in editor

When a run failed, click Debug in editor. Pinnora copies that run's data into the editor and pins it on the nodes that ran. Now you can open the failing node, see the exact input it got, change its parameters, and click Execute step until it works. You do not need to wait for the trigger to fire again.

For a run that worked, the same button reads Copy to editor. Use it to build the next change on real data.

Remember to unpin the data when you are done if you want later tests to run those nodes fresh.

Retry

Retry runs a failed execution again. You get two choices:

• Retry with current version. Uses the version that is live now, including any fix you published.
• Retry with original version. Uses the version that was live when the run first failed.

Version history

Each publish saves a version. Pinnora also saves your draft as you work. Open Version history from the top bar to see every version with its date and author. You can compare two versions, give one a name, download it, clone it into a new workflow, or restore it. Restoring saves your current draft as a version first, so nothing is lost.

Common causes of failure

• A disconnected account. Reconnect it in Integrations, then retry.
• Not enough credits. Top up, then retry.
• A budget was reached. Raise the budget in settings, or lower what the run makes.
• An empty field. An expression pointed at a field that was missing for one item. Open the node in Debug in editor to see which item.