Update Successful transaction with additional information

Help Studio
,
1

Hi,

I have a concern about the handling time of transactions. Currently, when we update a transaction by adding additional information to it, the handling time seems to reset, regardless of whether the transaction was previously marked as “Failed” or “Successful.” This is causing our data to be skewed, as we are unable to accurately determine the time it takes to book an order. Instead of 3 minutes we have an average handling time of 40.

I find it puzzling that the first status update does not lock in the average handling time, and the second status update has a significant impact on it. Is there any other way to add additional information to a transaction without resetting its status?

We have two jobs involved in this process. The main job books orders for transactions and marks them as “failed” or “successful” with an additional field for the new order reference. The second job, which is temporary, reconciles the transactions from the last hour and updates the transaction analytics with a new field indicating whether the transaction was reconciled or not. We don’t want to keep the transaction in an “In progress” state until it’s reconciled because it doesn’t accurately represent what we want to calculate. The true job is booking the order, and that is the time that should be reflected.

We were hoping that once the transaction is initially set to “Failed” or “Successful” after booking, it would lock the average handling time in place. However, this doesn’t seem to be the case.

I would greatly appreciate any insights or suggestions on how we can address this issue and ensure that the handling time of our transactions remains accurate throughout the process.

2

Hello @AssociateDev

  1. Manage transaction states accurately.
  2. Review and correct your status update logic.
  3. Separate transaction data from additional information.
  4. Calculate handling time based on the original start time.
  5. Implement logging and auditing for tracking changes.
  6. Ensure the second job for reconciliation doesn’t affect handling time.
  7. Review UiPath Orchestrator settings if applicable.

Thanks & Cheers!!!

3

Hi, I am not really sure what do you mean.
At the moment we are utilizing both transaction data, output and analytics. Transaction data holds the initial transaction information. Once transaction is loaded, using transaction data bot is booking an order. Once the order is booked, it marks the transaction as successful and updates the output data with the new order number. All this part for us seems logical.

However, once the second job reads the queue and goes on to reconcile, after reconciliation it updates the analytics of the transaction so that the reconciliation would be reflected on the transaction as a whole - it is useful for us for analytics and reporting. If we won’t do that, then the second job will be on constant loops working with the same transactions over and over again. At the moment the only way to add the new field is by using the set status activity again on the transaction - I made it so it uses the previous status “for successful to keep successful” and just add a new field, but that makes the queue then calculate the handling time from “new” status until the last status change, even though it was already previously set as “failed” and successful.

I was hoping I am missing something and there is a way to add additional information to the transaction without setting its status again