Error says this action requires folder (sometimes)

Hello,

I am wondering if anyone else faces this issue and there is any idea why this is? Will it become required always in the future? Standard activities like Get Transaction Item in REF or Get Queue Items fails sometimes if folder path is not assigned. This creates a huge problem for us because we have DEV / PROD seperation via folders and not in tenant so if folder name is required to use this activities in the future then we need to re-evaluate how we should structure this. And i understand that there is different thoughts in regards to DEV/PROD environment and that folder container structure is best for separation between say for example departments.

Best Regards
Marcus

@Ninjabullen

Ideally its not mandate …it picks the current folder it is in

try keep them in retry with a delay…we dint see such issues…is it happening for any older processes or so? if so try to upgrade the packages..also when you upgrade few activities due to version compatibilites might fail…so you might need to replace

cheers

@Ninjabullen

Yes, I did observed the same specially while debugging older code.

You can select the folder in your activities from dropdown and then from the process in Orchestrator, you will get option to choose the queue from the specific folder you want.

Great answers, many thanks for these. Do someone know if the folder will be mandatory field in the future or if this is only a bug that has occurred?

@Ninjabullen

As @ashokkarale mentioned it might be an issue in older code try to upgrade to letest version

in latest version I dont see it as mandate atleast my studio 24.10.x

cheers

@Ninjabullen,

It’s better to configure the folder for newer development so it will be configurable from the process.

Kindly close the thread by marking the answer as solution! Cheers!

Hello, we have also had this issue after we updated our studio to the latest STS version. This fix is hitting the refresh button on the bottom (image attached)

I’ve been having it on the LTS version, I dunno why its happening but the connection to the Orchestrator seems to be slipping, it also affects it when you try to publish to the orchestrator as the feeds in the orchestrator dont show and it only offers the custom location.

Hitting a refresh like David_Hernandez2 suggests resets it. It hasnt seemed to affect any unattended robots of mine, just Studio

Awesome, thanks for showing me the refresh button for the project. I have totally missed that so close and open again was what i was doing before.