How to bulk reprocess Successful Queue Items from a previous month after an application issue was fixed?

Help Orchestrator
1

Hi everyone,

We have a monthly UiPath bot that processes items through an Orchestrator Queue.

The bot ran successfully, but due to an application issue, some items were not processed correctly. The application issue has now been fixed.

However, all the affected Queue Items are already marked as Successful.

What is the best way to bulk reprocess these items without changing the original Queue Items?

Can we clone/requeue the successful items into a separate queue and run the bot again?

Looking for the recommended approach in UiPath Orchestrator.

Thanks!

2

Hi @Nellutla_Yaswanth_CGI ,
Best Practices you can follow:

  1. Identify the affected successful queue items.
  2. Extract their reference/data using Orchestrator API, Data Service, or a small utility workflow.
  3. Add them as new queue items into:
    • The same queue (with a new reference), or
    • A separate “Reprocessing” queue (preferred for tracking).
  4. Run the process again against the newly created queue items.

Why use a separate queue?

  • Maintains audit/history of original successful transactions.
  • Easier tracking and reporting of reprocessed items.
  • No impact on production queue statistics.
  • Cleaner root-cause analysis.

Project recommendation: Create a small recovery workflow:

  • Read affected successful transactions.
  • Create new queue items in a dedicated Reprocess Queue.
  • Include original QueueItemId/Reference in SpecificContent for traceability.

Thanks

3

Hi @Nellutla_Yaswanth_CGI,

First, check whether Unique Reference is enabled for the Queue. If Unique Reference is not enabled, you can run the Dispatcher bot with the same data (Email, excel etc), and the same transaction will be published again in New state.

If Unique Reference is enabled, follow the approach below:

  1. Open the Orchestrator Queue and go to View Transactions.
  2. Select the required transactions and click Export. (Exporting all the rows so need to remove addtional row if any.)
  3. Unzip the downloaded file and open the CSV file.
  4. Remove all columns except shown in the snapshot below:

image
image436×125 4.28 KB

  1. Update the Reference with a new value, for example, append _N to the existing reference.
  2. Make sure the data is in the correct format. Remove unnecessary {} and DynamicsProperties from Specific Data column. It should not look like below:

image

  1. Save the CSV file.
  2. Upload the CSV using Upload Item to the Queue .

This way, the original successful Queue Items remain unchanged, while the affected items are added as new transactions for reprocessing.

Thanks!

4

Hi @Nellutla_Yaswanth_CGI ,

If you don’t want to make any changes to the original queue, you can extract the required data from its transactions, add it to a separate queue, and then point your process to the new queue for processing.

Thanks.

5

@Nellutla_Yaswanth_CGI

You can bulk clone or export and import the items you want to add again

cheers

6

@Nellutla_Yaswanth_CGI

Do not need to do any manual work in this task, you can create a simple small workflow.

  1. First add Get Queue Items activity and set this filter to get all successful items.

image
image519×290 33.9 KB

Filter

image
image522×244 32.6 KB

  1. Then you add new activity Add queue items to add all items again to process as a new state.

Thanks

7

hiii @Nellutla_Yaswanth_CGI

If the Queue Items are already Successful, I would avoid modifying the original items.

A safer approach is to retrieve the affected Successful Queue Items based on the required criteria (for example, date range or specific reference/data), then create new Queue Items in a separate/reprocessing queue with the required data.

The bot can then process the new items normally, while the original Successful items remain unchanged for audit/history.

If the original QueueItem data is available through the Orchestrator API, you can also automate the retrieval and creation of the new Queue Items instead of doing it manually.