The selected connected machine does not reach the minimum required version of 21.10 to run cross platform processes

Hello guys,

hope you can help me with this one,
i have an app that takes internet message Id from outlook and put its information to Queue.
in the development tenant it works well, but it has an error in production tenant, to which i currently don’t understand.
your inputs are well appreciated, thanks!


@JomarieBancolo

As per error looks like the robot version on your production tenant is older which is creating an issue

can you confirm the version of the robot on the machine it is triggered

to identify the machine check for the job in jobs page or orchestrator

cheers

this is the robot that we have on our Development tenant: 26.0.182-cloud.21895
and this is on the production tenant: 26.0.190-cloud.22531

it seems that the production robot is newer than the development,
is it possible that this is our problem.

@JomarieBancolo

Does the version reflect on orchestrator?

to confirm the issue is not with machine can you manually start a process from jobs page on that machine

also on the job that failed can you show the error that you are getting

cheers

@JomarieBancolo In this case, the production robot being newer shouldn’t be the issue. The error is specifically about the connected machine not meeting the minimum required version (21.10 for cross-platform).

So I’d suggest checking a couple of things:

  • Whether the machine/template linked in Orchestrator is actually using that updated robot

  • If there are multiple machines/runtimes, maybe the job is picking an older one

  • Also double-check the runtime type (Unattended / Serverless / etc.)

Sometimes even if one machine is updated, the job might still run on a different connected machine with an older versio

Hello @JomarieBancolo,

Please verify the hostname where the job initially failed and check the robot version on that machine. Also, confirm which machine is picking up the job during resume (for safety, please verify all the robot versions assigned in the folder).

Since this is a HITL scenario, the job goes into a suspended state, and upon resumption it may be picked up by a different available robot. If that robot is running on a machine with an older version (below 21.10), it can cause this error.

Thanks,
Karthik