Option to start a runbook on a hybrid worker disappeared

Question

Dear Community, I am currently facing an unusual issue: An Azure Automation Runbook, which has always worked as expected on a hybrid worker, suddenly "lost" the option to be started on a hybrid worker. When I call the webhook, it responds with a "400 bad request", as the webhook was also configured to initiate the runbook on a hybrid worker. This issue arose after we activated the runtime environments. As demonstrated in the screenshots, the runbooks can still be run on the hybrid worker without any issues. Does anyone know a solution or has anyone experienced similar issues? Best Regards, Nils

Answer 1

You mention you have switched to using Runtime Environments, please note this item in the docs:

Currently only cloud jobs are supported for newly created runbooks linked to user-created Runtime environments. However, you can link the newly created runbook to system generated Automation Runtime Environment to execute it as a hybrid job.

So if this job is attached to a user created run time environment, then you cannot currently use a hybrid worker, You would need to use one the system generated environments.