Purpose to add annotations

@askvajrang i have dought with annotations wt the purpose we should create annotations please suugest me @Krishna_Raj

Hi @Mounika_Radharapu

Annotation is used to display a short message to the developer/business for why a particular sequence/workflow is created for. This helps the person viewing your code understand the usage of the sequence or understand the condition that’ll be applied to the “if” loop.

To create annotations, we can right-click on the Activity or sequence. Then click on Add annotations to write the specific message. If we have multiple activities inside the sequence/workflow you can receive what you look for. Follow the following steps to add annotations.

Now you can click anywhere and will notice the annotation just below the sequence.


You can add the annotations by using the shortcut keys Shift+F2

Hope it helps!!


Annotations help document your automation process. They provide clear explanations of what specific activities or sections of the workflow do. This is especially useful for anyone who might be reviewing or maintaining the automation later, including your future self.

Annotations can be extremely helpful during the debugging and maintenance phases. They can indicate why certain decisions were made, describe the expected behavior of activities, and point out any known issues or considerations

Annotations serve as a training tool for new team members. They can help newcomers quickly grasp the logic and structure of complex workflows.

In environments where compliance and auditing are important, annotations can provide a record of what the automation is supposed to do and why certain actions are taken, which is useful for regulatory purposes.


Annotations are for code readability and to mention logic about the activities/Sequence.

Here you can mention all the details about why/what/how logic. This would be crucial for other developers as well as your self also while debugging or fixing the issues in future.

Ashok :slight_smile:

Annotations in UiPath are comments or notes added to activities to explain what they do. These annotations help make the workflow more understandable for anyone who might be reading or maintaining the workflow in the future


I hope its help


-Annotations can serve as inline documentation, making it easier to understand the purpose and logic behind each activity.
-When you revisit a workflow after some time, annotations can help you remember why certain decisions were made or how specific parts of the process work. This makes it easier to update or modify the workflow.
-During the development and debugging phases, annotations can help you keep track of changes, reasons for certain configurations, or potential issues to look out for.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.