Debugging Activity Blocks
The below graphical representation highlights how UiPath Studio executes a block before stopping on it when debugging.
This is useful to understand when the block has already executed its actions, as the user is not able to step over it or into it.
Stepping into the block does not affect the activity, as it only stays highlighted. If you step over the block the next block is executed and the workflow continues.
Most programming shells execute and highlight a line when you step in or over it.
This is not the situation with Studio for the following reasons:
- It is based on Workflow Foundation technology, which is a framework specifically developed by Microsoft to execute activities; and
- Its debugging model is not identical to any other programming language, because the Workflow Framework is not offering these types of extensibility points.
Instead, UiPath Studio relies on workflow tracking information, that triggers a track notification for each of the following events:
- Activity started - Activity ended: the activity started event is triggered after it actually starts and this cannot be controlled.
If you want to stop before an activity executes entirely, you need to set the breakpoint on the previous activity instead.
A simple workflow example to help you get the picture:
- The breakpoint is set on a block that should close the error message displayed on the left.
- Click Step Into. Note that the error message disappears and Studio steps on the Click Button action and makes it active as in the screenshot below, although the action was already executed.
The passage describes the debugging process in UiPath Studio, explaining how blocks are executed and highlighted during debugging, and the differences between UiPath Studio's debugging model and other programming shells.
no_question
Given a text passage, determine:
    1. If it contains a mathematical question (including word problems or calculations)
    2. If an answer to that mathematical question is provided in the text

First, describe the content structure you found in 1-2 sentences.

Then provide your analysis in the following format:
TYPE: <one of the following values>
- NO_QUESTION
- SINGLE_QUESTION
- SINGLE_QUESTION_WITH_ANSWER
- MULTIPLE_QUESTIONS
- MULTIPLE_QUESTIONS_WITH_ANSWERS
system
Debugging Activity Blocks
The below graphical representation highlights how UiPath Studio executes a block before stopping on it when debugging.
This is useful to understand when the block has already executed its actions, as the user is not able to step over it or into it.
Stepping into the block does not affect the activity, as it only stays highlighted. If you step over the block the next block is executed and the workflow continues.
Most programming shells execute and highlight a line when you step in or over it.
This is not the situation with Studio for the following reasons:
- It is based on Workflow Foundation technology, which is a framework specifically developed by Microsoft to execute activities; and
- Its debugging model is not identical to any other programming language, because the Workflow Framework is not offering these types of extensibility points.
Instead, UiPath Studio relies on workflow tracking information, that triggers a track notification for each of the following events:
- Activity started - Activity ended: the activity started event is triggered after it actually starts and this cannot be controlled.
If you want to stop before an activity executes entirely, you need to set the breakpoint on the previous activity instead.
A simple workflow example to help you get the picture:
- The breakpoint is set on a block that should close the error message displayed on the left.
- Click Step Into. Note that the error message disappears and Studio steps on the Click Button action and makes it active as in the screenshot below, although the action was already executed.
user
The passage describes the debugging process in UiPath Studio, explaining how blocks are executed and highlighted during debugging, and the differences between UiPath Studio's debugging model and other programming shells.

TYPE: NO_QUESTION