Workflow Fails in Orchestrator But Works in Studio

This is the most common support issue. The root cause is almost always an environment difference between your dev machine and the Robot machine. Check these in order.

1. Hard-coded File Paths

If any activity uses a path like C:\Users\YourName\Documents\report.xlsx, it will fail on the Robot because that user does not exist there.

Fix: Use environment variable references like %USERPROFILE%\Documents\report.xlsx, or move the file to a shared network path.

2. Credentials

If the workflow uses a password typed directly into an activity, the Robot machine may have different credentials.

Fix: Store all passwords in the Orchestrator Secrets Vault and reference them with {{secret:name}}.

3. Missing Applications

The target application (e.g., a specific browser version or a line-of-business app) must be installed on the Robot machine. Check with your IT team.

4. Different Windows User Context

The Robot runs as a Windows service under a specific user account. That account may have different registry settings, folder permissions, or app configurations.

Fix: Log in to the Robot machine as the service account and run the workflow manually from Studio to reproduce the issue.

5. Browser Not Installed on Robot

Browser automation requires Chrome or Edge installed on the Robot machine. Install the same browser version used during development.

6. Relative Paths

Some file paths resolve relative to the Studio working directory on your dev machine but relative to a different directory on the Robot. Use absolute paths or the %APPDATA%\Genzbots folder which exists on every machine with Genzbots installed.

Golden RuleBefore deploying to Orchestrator, create a checklist: does the Robot machine have every application, credential, and file path the workflow needs? If you can run it manually on the Robot machine from Studio, it will work unattended.