I am adding queue items successfully in the Dispatcher workflow using Add Queue Item.
The items are visible in Orchestrator and all configurations (queue name, folder, tenant, and robot) are correct.
However, in the Performer workflow, when I use Get Transaction Item / Get Queue Item, it always returns “No transaction data”, and I am unable to retrieve any queue items.
Could someone please help me understand what might be causing this issue?
Check if you have set Postpone date for the queue items. this could be the only reason for this behavior.
Can you put a breakpoint at get transaction Item and check if you are getting here. Sometimes if you haven’t mapped arguments it correctly in Get Transaction Data workflow. So you might get no data.
Next, here only at get transaction item, you dont get data, means something with queue filters. By deafult this will queue items with “New” State. See in dispatcher where you are uploading queue items, if queue items are getting postpone. Try creating queue items with a seaprate test workflow and test the performer if it works
Where Is the Postpone , i don’t Get that
please refresh the queue. All items must be in New status to be picked by the Get Transaction Item activity. Items that are In Progress or Failed will not be picked.
If you face the same issue again, please recreate the queue, upload the items again, and retry the process.
i did EveryThing But it was don’t get The Transaction Data
Please share your Data Manager panel …
Something somewhere got modified for sure. As you are using the REFramework can you please try modifying the Queue name in the Config.xlsx file and use the below statement in the Get Transaction Item–> Queue name field - in_Config("OrchestratorQueueName").ToString
Update the folder name as well in the Config and pass in the Get Transaction Data like this - in_Config("OrchestratorQueueFolder").ToString
i already did this but i can’t get the data
Are you using Community license? @S_Yuvaraj
Same problem…All QUEUE activities work but not get transaction item
There was a bug in System package. Upgrade to package version 25.12.2 and this should work.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
