UiPath-ADAv1 Debugging and Exception Handling Practice Question
A developer is implementing a Global Exception Handler. Which TWO of the following statements regarding the behavior of the handler are correct?
⚠ Common exam trap
Candidates mistakenly believe the Global Exception Handler can only abort workflows, overlooking its powerful capabilities to retry activities or ignore errors.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
It can be used to retry the activity that caused the error by setting the error action to 'Retry'.
The Global Exception Handler is a powerful tool for managing unexpected errors in UiPath. It allows developers to define a standard recovery strategy, such as logging, retrying, or aborting. Understanding that it can modify the error status or force a retry is critical for building resilient automation that can handle environmental instability without requiring extensive individual try-catch blocks throughout the entire process.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
It can be used to retry the activity that caused the error by setting the error action to 'Retry'.
Why this is correct
Setting the errorAction argument to 'Retry' instructs the workflow to re-execute the specific activity that threw the exception. This is a common pattern for handling transient issues like temporary network disconnects or UI element loading delays in enterprise automation projects.
- ✗
It only executes if a Try-Catch block is present in the main workflow.
Why it's wrong here
The Global Exception Handler is designed to capture exceptions that are not caught by any local Try-Catch block within the project. It acts as a safety net for the entire execution, meaning local handling is not a prerequisite for its invocation.
- ✓
It can be used to ignore an exception and continue execution from the next activity.
Why this is correct
By setting the errorAction to 'Continue', the developer can instruct the robot to ignore the specific fault and proceed to the next activity in the workflow. This is useful for non-critical errors where processing can safely continue despite a minor failure.
- ✗
The handler can only be invoked once per project execution.
Why it's wrong here
The Global Exception Handler can be invoked multiple times during a single project execution if multiple uncaught exceptions occur. It is not restricted to a single use, as it provides a persistent mechanism to manage unexpected errors throughout the entire lifecycle of the robot.
- ✗
It must be triggered manually via an Invoke Workflow activity.
Why it's wrong here
The Global Exception Handler is automatically triggered by the UiPath runtime whenever an uncaught exception is raised. It is registered within the project settings and does not require manual invocation, ensuring it remains an always-on feature for error handling and logging.
About these practice questions
One of 285 original UiPath-ADAv1 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official UiPath exam blueprint
This UiPath-ADAv1 practice question is part of Courseiva's free UiPath certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the UiPath-ADAv1 exam.