I am using the Orchestrator Manager tool to manage credentials that need to be reset every six months and have been using it to this for a couple years now. Last week I used it to reset test credentials in our test and UAT tenants, which worked fine, and this week I need to use it for production. The issue I am facing is that it is failing every time when trying to retrieve the folders in our production tenant.
I can get past the authentication popup using the App ID and secret (same as my other tenants) and then get to the popup and select the Get Credential option.
I have tried versions 2.4.1 and 2.6.2 and in both I am able to successfully use it in both our test and dev tenants but our production tenant only gives the error.
I tried creating a new External application giving all Orchestrator permissions under application scope and am still facing the issue using this app id/secret as I am with the old one.
Is there any tenant-specific settings I can look at that would affect this? I donât know of any specific changes that have happened since the last time I ran this that would have only happened in production and not our test/dev tenants.
to know the issue..try to debug instead of runâŠcheck the variable values being sent into the activity that is failing and see if something might be off..or folder name or ID can be seen
I appreciate your response, that is a good idea and I gave it a try. The error is occurring during the workflow MakeHTTPRequest and is being thrown due to a status code not equal to the expected.
Here is where it failed along with the variables/arguments I can see, the in_ExpectedStatusCode of 200 is not equal to the out_StatusCode of 404 received from the HTTPRequest before it above resulting in the throw.
I set a breakpoint here and tried with a different tenant and the status codes matched but the rest of the in arguments look basically the same, aside from the URL using the other tenant name.
Looking above at the HTTP request that assigned out_StatusCode it looks like it should be using the exact same activity as the request I sent for the other tenant that works fine, it was a get method with in_OUID equal to 0.
It just seems like itâs unable to communicate with one tenant vs. the others and I donât know whyâŠI have tried using both upper and lower case when entering the tenant name in case there is something wrong there, and I have looked for spaces in the tenant name that maybe I didnât see but it is a single word with no spaces so looks normal to me.
After doing some more debugging I found what the issue was. There was an automatically created sub-folder called âDebug_Solutionâ under the âMy Workspaceâ folder that seems to not be treated the same by the API request and was causing the failures. I debugged and ignored the errors and it eventually ran completely through getting all the credential assets I needed.
I didnât need this folder so I deleted the folder and ran again and it ran perfectly. I had no idea where this folder came from so looked around and eventually found it is automatically created when you press âdebug in cloudâ in Studio web, which I did to test something for a citizen developer question.
So this was my fault for not knowing I did something to create this folder, but also probably a bug with the way these folders are created that they cause this kind of failure by behaving different from all other folders in the tenant. Hopefully this helps someone if they ever run into this issue.
