Help on understanding the relation of queue item status and different processing exceptions

Can anyone explain what the status of the queue is when a system exception occurs, and what happens to the queue status in the case of a business exception? I’d like to understand the differences between how each type of exception impacts the queue.

Each type of exception how it will impact is depending on how you want to handle them!

For both the exception in re framework the queue status will be updated as FAILED.

The exception type will be visible in exception column of queues. The exception type like business / application etc will be visible here

Now if you want to add retry logic in code
The system exception entries will be retried and added with status NEW.

No need of retry logic for valid business exception

Hope this help :blush: @Spoorti_Vijapure

@Spoorti_Vijapure

Welcome to the community

for system exception if auto retry is enabled for the first cases/transaction it will be retried…and if no auto retry is there or in auto retry last item the status will be failed

for business exception always it is failed

Hope this helps

cheers

@Spoorti_Vijapure,

Here is brief summary for this.

1 Like

Hey @Spoorti_Vijapure
When a system exception occurs in UiPath, the status of the queue item is set to “Retried” if the retry mechanism is enabled. If retries are exhausted or not configured, the item will ultimately be marked as “Failed”. On the other hand, when a business exception happens, the queue item is marked as “Failed” immediately without retries, as these exceptions usually indicate an issue with the data itself rather than a system error.
Orchestrator - Queue Item Statuses

Hi, @Spoorti_Vijapure

Fallow the steps below. If I helped you, please market is solved.

When an exception occurs in a queue in UiPath, the status of the item changes according to the exception type:

System Exception:

When a system exception occurs (problems such as network failure, application error, etc.), the status of the queue item changes to “Retried” (if there are still attempts) or “Failed” (if the attempts are exhausted).

If configured for multiple attempts, the item will be processed again. Otherwise, it will be marked as a permanent failure.

Business Exception:

A business exception occurs when there is a problem with the data (such as invalid or unexpected information). In this case, the status of the item changes directly to “Failed”.

Items with business exceptions are not reprocessed, since the error is in the data and not in the system.

Main difference: In a system exception, the item can be reprocessed (depending on the retry configuration), while in a business exception, the item fails without reprocessing.

1 Like

Hi @Spoorti_Vijapure ,

Adding to the above, this document below link also helps you additionally to gain better knowledge on Exceptions
About Exceptions

Also at the left side pane, click on various queue related topics

let me know, if you have any questions. Thanks!

The final status for both queue items, whether a system or business exception occurs, will ultimately be marked as “Failed.” However, the interim status differs in the case of a system exception if auto-retry is enabled.

For example, if auto-retry is set to 2, the status would follow this sequence: New → Retried → New → Failed. This happens when the queue is set to retry once, and a system exception occurs twice in a row.

On the other hand, if auto-retry is disabled, the status for a system exception would go from New → Failed, just like it would for a business exception.

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