Not able to get the data from the Queue

Help Orchestrator
,
1

Hi Folks,

I am trying to get my transactions from an Orchestrator Queue and the bot is failing at the Get Transaction Item workflow with an warning.
And the warning is see the the below picture
image

Does anyone have an idea what this error is?

2

@pradyumn.agrawal1,

It’s network issue. Check if your bot is connected to Orchestrator and allowed to go through the firewall.

Thanks,
Ashok :slight_smile:

4

Yes its connected and Licensed,

how can I check the Firewall?

5

I assume you kept the Get Transaction Item in the Retry scope?
Then you need to validate the actual error in Get transaction using try catch block inside retry scope.

If not can you share the screenshot of the code.

6

image
image620×760 19.1 KB

image
image497×819 18.3 KB

8

Any idea,
I have share the screenshot from the Get Transaction

9

@pradyumn.agrawal1,

If it’s connected then it’s good.

Try upgrading the packages to latest possible version. Apart from this, I don’t see any issue in your configuration.

Thanks,
Ashok :slight_smile:

10

@pradyumn.agrawal1

  1. First check if the issue is with only getting transaction for that queue or all
  2. check if the robot user has access to the queue and the folder containing queue
  3. is it occuring intermittently ? if so then check the orchetsrator server of on on prem installation to see if it is down during that time

cheers

11

Hi @pradyumn.agrawal1

The queue might be empty, meaning there are no transactions available to be processed.

Check the queue in Orchestrator to see if there are any pending or new items.
Ensure that transactions are being added to the queue correctly before the bot attempts to retrieve them.

The name of the queue specified in the “Get Transaction Item” activity might be incorrect or misspelled.

Double-check the queue name in both the Orchestrator and the workflow to ensure they match exactly, including case sensitivity.

Thanks,
Purushotham

12

The Initstate is working fine, I created the dummy bot and tried with multiple queues still the same error.
The bot is connected properly and it is Licensed as well, the process is showing correctly in the Assistant.
If I install a new process that will also come in the Assistant, the only problem is getting the data from the orchestrator.

13

I just double checked everything is right and there is no spelling mistake

14

@pradyumn.agrawal1

Please check the user roles and provide the queue level and transaction level roles and check

To verify try to do a get asset and check if you are getting data

please confirm your studio and orchestrator versions and deployment methods

cheers

15

Check Queue Name in Config if that’s right also try checking filters if applied any while getting queue item
Check Robot is configured properly and is connected
check if new items are present in queue

16

Its working fine in the Dev environment with Dev Orchestrator but not with the Production.
Orchestrator Version:- 2023.10.4
Studio Version:- 2022.10.10

17

@pradyumn.agrawal1

it looks like orchetsrator endpoint is being blocked …can you try running on any other machine

cheers

18

just another info
I am using windows process not windows -legacy.
Do you think this might also cause the issue?

19

Anyways I tried with Windows-Legacy as well still "No Luck :frowning: "

20

@pradyumn.agrawal1

Windows or legacy both should work

cheers

21

I created 2 process 1 with Windows and other one Windows Legacy and removed the Orchestrator Folder from both of them
It worked smoothly for Legacy but for Windows I am getting the same error.
Check the below screenshot

image
image841×654 21.6 KB

Am I doing anything wrong here?
I also removed the Arguments from the Main.xaml for the orchestrator Folder path