UiPath-ADPv1 Generic Automation Development Practice Question
A developer is building a REFramework-based process. The transaction data is stored in a Queue named 'Invoices'. During the Process Transaction state, the developer needs to mark a transaction item as Failed with a specific reason so that it will be retried according to the queue's MaxRetryNumber. Which activity and setting should be used inside the Catch block of the Process Transaction state?
⚠ Common exam trap
The trap here is thinking a failed transaction should be deleted or re-added, when the queue's native retry counter only works through Set Transaction Status.
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
✓
Use Set Transaction Status with Status set to 'Failed' and provide the exception reason.
Set Transaction Status with a Failed status is the correct way to record an exception against the current queue item while preserving its retry counter. When MaxRetryNumber is configured, Orchestrator re-queues the item for the specified number of attempts. Creating, deleting, or falsely succeeding the item all break the queue's built-in retry and reporting behavior.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Delete Queue Item to remove the failed item and rely on Orchestrator to regenerate it.
Why it's wrong here
Deleting a queue item removes it permanently from the queue. Orchestrator does not regenerate deleted items, so the transaction would be lost and never retried. This action also discards the failure reason, making troubleshooting impossible and violating the intended retry behavior.
- ✗
Use Set Transaction Status with Status set to 'Successful' and write the error to a log file.
Why it's wrong here
Marking a failed transaction as Successful tells Orchestrator the item completed correctly, so it will not be retried and the failure is hidden from queue analytics. Logging the error does not compensate for the incorrect status, and downstream reporting would treat the item as processed, masking the defect.
- ✓
Use Set Transaction Status with Status set to 'Failed' and provide the exception reason.
Why this is correct
Set Transaction Status with Status Failed records the failure against the current queue item and increments its retry counter. When the queue's MaxRetryNumber is greater than zero, the item is re-queued for another attempt until retries are exhausted. This is the standard REFramework behavior for handling business or application exceptions that should be retried.
- ✗
Use Add Queue Item to create a new transaction item with the failure details in the reference field.
Why it's wrong here
Add Queue Item creates a brand-new queue item rather than updating the current one. The original transaction would remain In Progress or be abandoned, and the new item would not inherit the retry counter or the original item's data. This approach duplicates work and breaks the queue's retry semantics.
About these practice questions
One of 276 original UiPath-ADPv1 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-ADPv1 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-ADPv1 exam.