UiPath Documentation
  • ST-DBP-003 - Empty Catch Block
  • ST-DBP-007 - Multiple Flowchart Layers
  • ST-DBP-020 - Undefined Output Properties
  • ST-DBP-021 - Hardcoded Timeout
  • ST-DBP-023 - Empty Workflow
  • ST-DBP-024 - Persistence Activity Check
  • ST-DBP-025 - Variables Serialization Prerequisite
  • ST-DBP-026 - Delay Activity Usage
  • ST-DBP-027 - Persistence Best Practice
  • ST-DBP-028 - Arguments Serialization Prerequisite
  • Variables
  • Arguments
  • Imported Namespaces
  • Coded automations
  • Trigger-based Attended Automation
  • Control Flow
  • Object Repository
  • Logging
  • The ScreenScrapeJavaSupport Tool
  • Studio testing
  • Extensions
  • Troubleshooting
  • UiPath logo, featuring letters U and I in white

    Studio user guide

    Last updated Apr 7, 2026

    ST-DBP-003 - Empty Catch Block

    Rule ID: ST-DBP-003

    Scope: Activity

    Description

    The rule checks whether exceptions are caught with a purpose, and not only to prevent error messages.

    Recommendation

    It is recommended to insert log messages in the Catch block of a Try Catch activity, in addition to the exception handling itself.

    Refer to the Project Organization page to learn more about how to handle errors and use Try/Catch blocks.

    docs image

    • Description
    • Recommendation

    Was this page helpful?

    Connect

    Need help? Support

    Want to learn? UiPath Academy

    Have questions? UiPath Forum

    Stay updated