Avoid assigning new job to a machine that is failed multiple time recently

Is there a setting in orchestrator to stop or avoid assigning new jobs to a Machine that is failed multiple times recently?

Hi @nabaraj.subedi,

maybe not exactly what you are looking for but you can define several time frames for jobs in several conditions to stop or kill them:

…another possibility (away from Orchestrator) would be to limit the number of retries in the project directly.

Disable those robots.

I was looking for a solution for time between job starts to get failed on Bot machines and orchestrator sends notification or for the night when no one is monitoring jobs, so that it does not effect other pending work items in queue.