UiPath Error Handling and Debugging Flashcards

What does the 'Continue on Error' property on a UiPath activity do when set to True?

Answer: Allows the workflow to proceed to the next activity even if the current one throws an exception

Setting Continue on Error to True suppresses any exception thrown by that activity and allows workflow execution to proceed normally.

In UiPath, what type of exception should you throw when a business rule is violated (e.g., invoice amount is negative)?

Answer: BusinessRuleException

BusinessRuleException is a UiPath-specific exception type used to flag data or rule violations, marking queue items as Business Exception in Orchestrator.

What is the 'Log Message' activity used for in UiPath?

Answer: Sending a log entry with a specified severity level to the robot's output and Orchestrator logs

Log Message writes a text message at a chosen level (Trace, Info, Warn, Error, Fatal) to both Studio output and Orchestrator's Logs section.

Which UiPath debugging mode runs the workflow slowly with each activity highlighted to help spot timing issues?

Answer: Slow Step

Slow Step mode executes the workflow with a configurable delay between activities, highlighting each one as it runs for visual tracing.

What is the purpose of the 'Finally' block in a UiPath Try Catch activity?

Answer: It always runs after Try and Catch, regardless of whether an exception occurred

The Finally block executes unconditionally after the Try and Catch sections, making it ideal for cleanup tasks like closing browsers or files.

In UiPath, what happens if an exception is not caught by any handler in the workflow hierarchy?

Answer: The exception propagates up to the caller or Global Exception Handler; if unhandled there, the job fails

Uncaught exceptions bubble up through invoked workflow callers; the last resort is the Global Exception Handler, and if that doesn't handle it, the job terminates with a fault.