Excluding Nodes in SAS Studio Flows: A Smarter Way to Test, Debug, and Iterate

[#1]

When building complex flows in SAS Studio, repeatedly running every step just to test a small change can quickly become frustrating. Whether you are debugging a transformation, validating intermediate results, or experimenting with new logic, rerunning unnecessary nodes slows development and makes troubleshooting harder.

The Exclude from run feature, introduced in Stable 2025.12, helps streamline this process by allowing you to temporarily skip selected nodes during execution. This post explains how it works, when to use it, and practical examples of how it can simplify your flow development.

Running Flows in SAS Studio

In SAS Studio, each node in a flow represents a step such as importing, querying, transforming, or exporting data. During development, you can:

• Run the entire flow to execute all nodes in sequence
• Run a single selected node to validate a specific step
• Run nodes downstream to execute the selected node and everything that follows
• Run nodes upstream to prepare input data without running the selected node itself

The Exclude from run feature adds even more flexibility by allowing you to temporarily skip selected nodes during execution. Excluded nodes remain part of the flow but are not run, making it easier to test and debug flows without repeatedly executing unnecessary steps.

Excluding a Node from a Flow

To exclude a node from running, right-click the node on the flow canvas and select Exclude from run. The node appears disabled on the canvas, making it clear which steps will be skipped.

In the example shown, the flow imports and prepares customer loan data through several transformation steps before splitting the data by loan type and exporting the results to Excel.

Select any image to see a larger version.
Mobile users: To view the images, select the "Full" version at the bottom of the page.

When refining a flow, you might make changes to an upstream node such as Calculate Columns or Add County_X_Y and want to validate the transformed table output without repeatedly running the export process. To achieve this, right-click on the node labelled Export to Excel and select Exclude from run. 

If the Export to Excel node is excluded, the flow still processes and creates the intermediate output tables, but the Excel export step is skipped. This allows you to validate upstream transformations without repeatedly generating output files, reducing run time and speeding up iteration.

Excluded nodes remain part of the flow design and can be re-enabled at any time. However, you should avoid excluding nodes that are required for downstream processing, as this can result in errors or incomplete outputs.

Real-World Examples

Excluding nodes can simplify several common development tasks, from troubleshooting flows to reducing unnecessary processing while testing changes

• Debugging a Broken Flow: If a flow fails after adding a new node, you can exclude that node and run the flow again. If the flow succeeds, you have quickly identified the source of the issue.
• Testing Data at Different Stages: If your final output looks incorrect, you can exclude downstream nodes to inspect intermediate results. For example, excluding a calculation step allows you to validate the data produced by a join before further transformations are applied.
• Improving Performance During Development: Export steps, large aggregations, or complex calculations can add unnecessary run time while you are still refining upstream logic. Excluding these nodes allows you to iterate faster and focus only on the parts of the flow you are actively developing.
• Comparing Alternative Logic: If you want to test a new approach, you can exclude an existing node and add a new one alongside it. This allows you to experiment without deleting or rebuilding your original logic.

Considerations When Excluding Nodes

Excluded nodes are skipped during execution but still remain part of the flow design, so it is worth keeping dependencies in mind when testing changes.

Table nodes cannot be excluded from a run, and excluding nodes that produce data required by downstream steps can result in errors or incomplete outputs. For example, if an excluded node creates a column that is referenced later in the flow, subsequent nodes may fail during execution.

When working with excluded nodes, it is a good practice to:

• Check whether downstream nodes depend on outputs from the excluded nod
• Re-enable excluded nodes before production execution if required
• Keep flows organized and clearly labeled to simplify troubleshooting and maintenance

Final Thoughts

Exclude from run is a small feature, but it can have a big impact on day-to-day flow development. By allowing you to selectively skip nodes, SAS Studio makes it easier to troubleshoot issues, validate transformations, and iterate on complex flows without constantly rerunning the entire pipeline.

For teams building larger and more sophisticated flows in SAS Viya, this added flexibility can make development faster, cleaner, and significantly more efficient.

What scenario will you use it for? 

Find more articles from SAS Global Enablement and Learning here.