400 (Bad Request)

Help Test Cloud
1

Hi All,
I’m running test case on test manager. While running, it stops midway for the process. Here’s the error on the logs: "400 (Bad Request). Orchestrator response: "Error {“message”:“USD Intra Branch Transfer - Invoke Workflow File (Intra Branch Transfer.xaml): Status code: 400 (Bad Request). Orchestrator response: \r\nFolder does not exist or the user does not have access to the folder. Error code: 1100\r\nin Framework\InitAllApplications.xaml\r\n at InvokeWorkflowFile "USD Intra Branch Transfer - Invoke Workflow File (Intra Branch Transfer.xaml)"\r\n at Sequence "Cash Management Intra Branch PESO and USD”

Hope you can help me!

Thank you.

2

Hey,
Can you check the folder whether it is correct?

3

Here’s the folder for Studio
image
Orchestrator(with highlight)

image
image1897×486 78 KB

4

Okey so folder is exist. What about automation user that you run on?
Go through Orchestrator → Folder → Settings and check the user and its role

5

Hi @rpaforum

The error means the process is trying to access an Orchestrator folder that doesn’t exist or the robot/user doesn’t have access.

  • Checking the folder exists and the name matches exactly.
  • Ensuring the robot or user running the test has access to that folder.
  • Verifying the test case in Test Manager points to the correct folder.
  • Making sure the workflow file paths in Invoke Workflow File are valid.
6

Hi,

All of these are applied and still when I’m running the bot stops midway. After running to the first part of the process. The bot will stop immediately. I tried comment out the part that errors(publishing another package). Yet still errors after the first part of the process.

Is it normal that the first part is running and the latter part is not working because of the folder access issue?

7

{ABF41F0C-54EE-42F0-83C3-BF72054E21F1}
{ABF41F0C-54EE-42F0-83C3-BF72054E21F1}1907×436 60.3 KB

8

Yes, this is normal behavior.

The first part runs because it doesn’t immediately need a new Orchestrator folder check. When the process reaches a step that requires Orchestrator access, the folder validation happens and fails with Error 1100.

  • The job can start and run partially even if the folder access is wrong.
  • It fails only when Orchestrator needs to resolve the folder again.
  • This usually means a folder or permission mismatch between Test Manager, the process deployment, and the execution user.

Try running the process manually from Orchestrator in the same folder used by Test Manager to confirm the issue.

9

Hi @rpaforum

Are you able to show in your code where you have specified the folder name?

Is it same as in orchestrator?

10

Yes, it’s in the same folder.

11

Hi,

May I know how can I run manually from the orchestrator? There is a notification on orchestrator that the activities related to testing will be moved on Test Manager.

Thank you

12
  1. Go to Orchestrator → Automations → Processes
  2. Select the folder used by your Test Manager test
  3. Find your process and click Start
  4. Choose the same user/robot used in Test Manager
  5. Run it and check if the same error appears

If it fails the same way, the issue is definitely folder or permission mismatch.
If it runs fine manually, then the Test Manager → folder mapping is incorrect.