Why did this exception occur? The item is getting stuck in the queue

Help Orchestrator
,
1

When starting the bot, I am encountering the following exception: " Set to business exception due to item getting stuck in the queue. Please verify the outcome in the logs before retrying."

I checked the logs, but no entries are being created for this issue.

Forum Engagement Daily Reports
2

@Praveen_Soni,

Bot is facing some issue while set status to business exception.

Try to replicate the issue why it’s facing this issue. Check for the exception message contains any invalid characters or length is very long.

Thanks,
Ashok :slightly_smiling_face:

4

[quote=“Praveen_Soni, post:3, topic:762290”]
Hi @ashokkarale , I checked, but there are no messages related to invalid characters or excessive length. The only message I found while checking the queue status was “Set to business exception due to item getting stuck in the queue. Please verify the outcome in the logs before retrying.”

please refer the screenshot

image
image896Ă—233 22.4 KB

5

@Praveen_Soni,

Are you getting the same error while debugging from Studio as well?

Thanks,
Ashok :slight_smile:

6

@ashokkarale - No, I did not get an error while debugging from Studio.

I just want to understand the cause of the error, actually what happened for these transactions.

Here is the full scenario: I ran one process bot on three accounts due to the high volume of transactions. I used the same machine with three different accounts. Initially, one bot started processing the transactions, and for 30 seconds, the other two machines were in a pending state. After one minute, all three machines were working in parallel. However, when I checked the queue, I found four transactions showing this error: “Set to business exception due to item getting stuck in the queue. Please verify the outcome in the logs before retrying.”

Thanks,
Praveen Soni :slightly_smiling_face:

7

@Praveen_Soni,

Ohh ok that’s strange. What was the QueueItem status? If it was Failed, I suspect there would be some network latency which could have resulted in this. In first attempt, bot would have tried to fail the transaction but after sending the request it didn’t get the response and retried the set transaction to set it to fail again on the transaction which got failed in first attempt.

I tried to reproduce this but not happening.

Thanks,
Ashok :slight_smile:

8

@ashokkarale,
Yes, the status was “failed.” It might have been due to network latency, which could have resulted in this issue.

Thanks,
Praveen Soni :slightly_smiling_face:

1 Like