Using the Debugger
Enhance your automation process development workflow with the debugger.
Last updated
Was this helpful?
Enhance your automation process development workflow with the debugger.
Last updated
Was this helpful?
The Debugger is a feature in the Kognitos platform designed to simplify the debugging process. It allows you to add breakpoints to start and pause your automation as needed, enhancing your development workflow and experience.
The debugger is available within the Playground and Processes. These steps outline how to use the debugger within the Playground:
Navigate to the Playground tab.
Open a playground by clicking on an existing name from your list or New Playground to create a new one.
Write and edit your automation inside the playground.
Hover over the left side of the line where you want to add a debug point. Click on the bug icon that appears.
After you click on the bug icon, two options appear: a Start and a Pause point. Click to enable either one:
Start: Will run the automation from this line.
Pause: Will run the automation until this line (the execution will stop at the line before). Example: If you set a pause point on line 10, the automation will stop after completing line 9.
Note: Be sure to add all pause markers before running the automation. New pause markers added while the automation is running will be ignored until the next run.
These are the markers used in the interface to indicate different states of execution:
Start: A green dot marks where automation execution will begin.
Stop: A red dot indicates that automation execution pauses before this line.
Paused: A yellow line marks where the automation is currently paused.
Multiple Breakpoints: You can add multiple breakpoints within a single run. Utilizing multiple breakpoints can significantly enhance your development workflow, making identifying and resolving issues within your automation scripts easier.
Execution Start Point: Execution is context-dependent and does not guarantee it will begin from a specified line. The system automatically adjusts the start point based on execution history and surrounding control structures.
Example: If the start point is inside a loop, the system can move the start line to the start of the loop.
