I have been using Community Orchestrator for a long time, with several processes running in two different Machines (each with Studio Robots).
But suddenly, when trying to run a new Job from Orchestrator (and / or through the API), there is no available Robot to chose. See the image below:
When using the API to start a new Job, the error message is “Undefined robots” #1678.
I have already checked that the robots are connected and licensed. Tried disconnecting and reconnecting several times.
I am still able to publish packages from Studio to Orchestrator, and to run jobs from Orchestrator through the Desktop Assistant.
Is there a known error that generates this problem? Anyone else experiencing something similar?