I’m encountering this error: Could not retrieve transaction item. Exception message: The given key 'OrchestratorQueueName' was not present in the dictionary. This occurs when retrieving transaction items from Orchestrator. The queue name is correctly configured, but the error suggests the ‘OrchestratorQueueName’ key is missing.
I’ve checked the configuration file and Orchestrator settings, but the issue persists. Any advice on resolving this or common causes for this error?
Check your config file. You have given the wrong name in the Name column. The key name has to be OrchestratorQueueName, but you have given OrchestratQueueName. Change the value in the Excel.
Also, and this is a shout-out to a lot of people on this forum the past years… spend some time reading and understanding error messages. The cause of the problem was in there.
More and more I see blind panic and posting a wide variety of errors and a plead for help. Nothing wrong with asking help, but after blindly copying a proposed solution and moving on with the rest of your project one learns nothing and the next speedbump means asking for help again.
In this example: your activity throws an error that a dictionary does not contain a key that is referred to.
So, find the dictionary. Check the current key/value pairs in it during debug mode, and compare it to what you are looking for. Voila, problem solved by just following the hint of the error message.
I don’t mean to be offensive here, but intend this more as a ‘teach a man to fish’ moment.
Question why you are even using this archaic config.
Abandon that Excel, and by that I dont mean start using a JSON file.
If you need to use an asset to get a queue name, just use it directly where you need it.
Question does the queue name even need to be handled via a config? If you assign it directly then the Orchestrator can actually validate if the queue exists.
I see most people hanging on to certain ways of working cause thats how they were taught when the reasons for working that way are no longer applicable or relevant.
This could have been entirely avoided by not using the old dictionary <string, string> config paradigm.
