Use the Debug Button
The Debug button will provide more information around the flow values while executing the pipeline. This can help identify where a pipeline is failing and which node or activity is causing the issue.
When troubleshooting a pipeline, it is often recommended to run the pipeline in Debug mode before executing it normally.
Disable Fast Execution
EnableFastExecution = False
When investigating issues, set EnableFastExecution to False.
Disabling Fast Execution can provide more detailed execution information and make it easier to identify where failures occur within the pipeline. While execution may take longer, the additional visibility can significantly assist with troubleshooting.
Run Individual Sections of a Pipeline
If a pipeline contains many activities, it can be difficult to identify where an issue is occurring.
Where possible, isolate sections of the pipeline starting from the beginning, building the flow as you go and execute smaller portions independently. This enables you to determine whether the issue is related to a specific activity, decision path, variable assignment, or process invocation.
Breaking a complex pipeline into smaller testable sections is often one of the quickest ways to identify configuration issues.
Review the Run Steps
Review the Run Steps panel to monitor pipeline execution and investigate any warnings, errors, or unexpected behaviour. The Run Steps view provides a detailed breakdown of each stage of execution, helping you identify where a pipeline has failed or produced unexpected results.
When troubleshooting, use the Run Steps panel to:
Identify the activity or node where execution failed. Review error and warning messages generated during execution. Examine SQL statements and database-related errors. Confirm that activities executed in the expected order. Verify that decision elements followed the correct execution path. Check execution times to identify potential performance bottlenecks. Locate and access activity-specific logs for more detailed investigation. Validate that variables, parameters, and activity outputs are producing the expected results.
Reviewing Run Steps should typically be one of the first troubleshooting actions performed when a pipeline does not execute as expected, as it can quickly narrow down the source of an issue before deeper investigation is required.
General Debugging Recommendations
Save the pipeline before testing changes. Test small sections of a pipeline before testing the entire workflow. Verify variable values throughout execution. Review any warnings as well as errors. Check activity-specific logs when troubleshooting failures. Use meaningful names for variables and pipeline elements to simplify debugging.
Note: Troubleshooting guidance is continually evolving. As new use cases and issues are discovered, additional tips and best practices should be added to this guide.