When you debug an automation, you have three function keys to use for navigating the...

When debugging automations in Pega Robot Studio, developers use specific function keys to control the flow of execution at breakpoints. Each key provides a distinct method for navigating through the automation logic during a debugging session.

According to the Pega Robotics System Design and Implementation Guide, section “Debugging Automations — Function Keys and Breakpoint Navigation”:

“During debugging, Pega Robot Studio allows you to step through the automation’s logic using three primary navigation commands:

F10 (Step Over): Executes the current step and proceeds to the next event or data link, without stepping into nested automations or sub-events.

F11 (Step Into): Executes the current step and enters any nested event link or sub-automation to debug internal logic.

F5 (Continue): Continues running the automation until the next breakpoint is encountered.”

Detailed Reasoning:

F10 – Step Over

Moves to the next automation event or data link at the same level.

Skips over nested or child automations while still executing them.

F11 – Step Into

Moves into the next automation event link or nested automation to debug its internal process.

Useful when you need to analyze detailed event flow inside another automation.

F5 – Continue

Resumes automation execution at normal speed until it encounters the next breakpoint or finishes.

Used to verify execution results after setting conditional breakpoints.

Final Correct Matching:

Navigation Rule

Function Key

Proceed to the next automation event or data link.

F10

Proceed to the next automation event link.

F11

Continue running the automation until the next breakpoint is reached.

F5