Hi!
Everytime I try to login into orchestrator cloud using a VM (I am currently using a mac, Windows is virtualized), the following error is throw:
A correlation failure has occurred. (#222)’
This is happening only within the VM (and multiple browsers), I can successfully login with the same user, but directly in the mac.
Do you have any suggestion?
Thanks in advance.
your timeframe is right?
@Forum_Chatbot can you advise on how to proceed when receiving this error message: A correlation failure has occurred. (#222)?
Based on our experience with Orchestrator and similar environments, this particular error – “A correlation failure has occurred. (#222)” – typically indicates that something in the authentication “handshake” or token exchange isn’t matching between what is expected by Orchestrator and what is received. This can often happen in environments where (for example) cookies, sessions, or certain headers aren’t persisting or being passed correctly. Given your situation (logging in on a VM versus directly on the host machine), here are a few steps you might consider:
Clear Browser Cache & Cookies:
Sometimes stale cookies or cached data can affect the authentication flow. Clear your browser’s cache and cookies on the VM and try again.
Check Browser Settings:
Ensure that your VM’s browser isn’t blocking or stripping out cookies or security headers. You might also want to check for any extensions that could interfere with the authentication process.
Time Synchronization:
Verify that the VM’s system time is correct. An incorrect time or timezone might cause issues with token validation if there’s a mismatch.
Network or Proxies:
If your VM is behind a different network configuration or proxy than your host Mac, ensure that nothing in the network path (like a reverse proxy or firewall) is altering the authentication requests/responses.
Orchestrator Settings:
In some cases, correlation errors can stem from discrepancies in security settings on Orchestrator (for example, related to cookies or session timeouts). Check if there are any known issues or specific settings related to the cloud version of Orchestrator that might influence authentication on virtualized environments.
Raise a Support Ticket if Needed:
If these suggestions don’t resolve the issue, consider raising a support ticket with UiPath. They might have specific logs or insights that can pinpoint why the correlation is failing in a VM setup.
While we haven’t seen a definitive “official” troubleshooting checklist for error (#222) in the publicly available documentation, these steps usually help resolve correlation issues in authentication workflows. If you have more logs (or can enable more verbose logging during the login attempt), that additional context could be very useful in diagnosing the exact root cause.
Hope this helps as a starting point for troubleshooting!
Sources:
─ UiPath Orchestrator Discussion on the UiPath Forum[1]