There is a bug with the Get Queue Items where if ‘Folder Path’ isn’t declared it’s not checking for queue in current running folder, it’s going for root folder in the modern folder tree
As you can see here i have a root folder name ‘Root’ this is where we have all our assets
in the sub folders is where we have all our queues so we don’t mix production and development data on the queue and stats side.
Get Asset will check for asset in the running folder, so if I run an automation from the development folder it will look for the asset in that folder, this was expected, so we changed the folder to check in “/” and bingo, it works as all our assets is in the ‘Root’ folder
Now i wanted to use the ‘Get Queue Items’ and expected the same behaviour but boy i was wrong
It will default to the root folder and if you try to define that it should look in the ambient folder by defining “.” or “./” in folder path it just throws the same error. Then for fun i tried to define folder path like this “/Development” forcing it to root and then ambient and it works. Then to verify that it is looking in the root folder as default i defined folder path like this “./Development” forcing it to start in ambient folder, and then go into development folder and this works, concluding that even if it is run from a subfolder like in this case, the activity ignores the real ambient folder.
I know of multiple ways to temp-fix this like arguments, config files and such, so i don’t have to release multiple version but that is not the point of this topic, the point is it should be looking in the ambient folder when not defined