actually my workflow is running in attended mode its not running in unattended setup why? iam getting this error in logs: The primary screen resolution is: 1366 x 514
Hi @naveen5
Go to your Unattended Robot settings in Orchestrator Robots page and change the screen resolution as per system you used in Development and then try once.
Regards
@naveen5 ,
It seems something is wrong before initialization. The message you mentioned is ReFramework first log. Bot is getting stuck right after that.
Sample logs for reference.

Thanks,
Ashok ![]()
Solutions:
- Orchestrator Settings:*
Resolution:* Match the unattended robot’s resolution in Orchestrator to the virtual machine’s resolution.
LogonToConsole:* Set toFalsefor unattended robots. - Workflow Optimization:*
Anchors:* Use the ‘Anchor Base’ activity to make targeting screen elements more reliable.
Keyboard shortcuts:* Use hotkeys instead of clicking on specific UI elements.
Robust Selectors:* Improve UiPath selectors to target elements based on unique attributes rather than screen position.
Remember:*
Citrix:* If you’re using Citrix, consider Citrix-specific UiPath solutions.
Testing:* Thoroughly test in an environment that exactly mimics your unattended setup.
i tried setting up resolution in orchestrator but no use its gets same primary resolution error?
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.