Hi @shlok_rpa
Step 1: Check Asset Scope in Orchestrator
-
Go to Orchestrator > Assets.
-
Locate your API key asset (e.g., OCR_API_Key).
-
Confirm:
The asset is Text or Credential, not both.
The asset is available in the correct folder.
It is linked to the right user and machine that executes scheduled jobs.
Step 2: Check Process Execution User
In Orchestrator > Triggers, look at the process trigger details.
See which robot and user is assigned to run the job.
Confirm that user has the same access to assets and config.
Example issue: You (developer) run it manually under DOMAIN\YourUser, but the trigger runs it as DOMAIN\BotUser who may not have access to the same assets.
Step 3: Log Asset Value Before Use
In your workflow before calling the OCR activity, add:
Log Message: "OCR API Key: " + yourApiKeyVariable
If it logs blank or null during triggered runs, then it’s a clear access or missing asset issue.
Step 4 :Check OCR Engine Configuration
For Google OCR, ensure the robot has access to the API key file or environment variable (e.g., GOOGLE_APPLICATION_CREDENTIALS).
Hope this answers finds well!