Pin or Unpin a Node Output

Pinning freezes a node's output so the debugger can reuse the same result in subsequent runs. Pinning is useful when debugging a final response node. If the retrieval or service step has already returned the correct data, pin its output and focus on improving downstream behavior. This saves time and avoids repeatedly running the same upstream node.

Use pinning in the following scenarios to reduce unnecessary execution and simplify workflow testing:

A stable upstream node doesn't need to run again.
A node consumes tokens or has a high execution cost.
A node calls an external service, data function, or tool.
You want to isolate downstream behavior.
You want to reproduce a scenario using the same input every time.

Use pinned outputs to speed up debugging by reusing previously generated results.

Go to AI Agent Studio and open the Workflows tab.
Select Edit to modify a workflow.
From the toolbar, select Debug .
Enter a prompt in Ask Oracle and submit it to run the workflow.
Run the workflow until the node produces a valid result.
Select the node.
Select the Results tab.
Select Pin output to pin an action, and the pin indicator is displayed on the node.

After pinning, subsequent debug runs can use the cached output instead of running the node again. Remove a pinned output when you want the node to run again and generate fresh results.

Go to AI Agent Studio and open the Workflows tab.
Select Edit to modify a workflow.
From the toolbar, select Debug .
Enter a prompt in Ask Oracle and submit it to run the workflow.
Run the workflow until the node produces a valid result.
Select the node.
Select the Results tab.
Select Overriding Output to unpin an action.
Run the workflow again to confirm that the node completes its run.