Folder 400 access error orchestrator

[adext01]

What could be the reason that a robot that was working fine suddenly gets folder access error ?

Status code: 400 (Bad Request). Orchestrator response:
Folder does not exist or the user does not have access to the folder. Error code: 1100

Nothing changed and folder name in activity is fine

[Anil_G (Anil Gorthi)]

@adext01

did you upgrase the robot or studio?

in latest versions there are few instances observed like that

ins tudio to clear try to refresh from right bottom and then run

cheers

[prashant1603765 (Prashant Kumar)]

Hi @adext01

This error occurs when the robot/account no longer has valid permissions or mapping to the folder, even if the name remains the same; it can be due to role changes, account‑machine mapping removal, or folder reassignment causing loss of access context in Orchestrator.

Happy Automation

[MohammedShabbir]

If you’re running it from Studio, try clicking Refresh (bottom-right corner) and then run the workflow again. This has resolved the issue in some cases.