Triggers Being Deactivated By The System Administrator

[system]

Why are triggers being deactivated by the System Administrator on the Orchestrator, when this type of user is not created?

• By default, a trigger gets disabled automatically after 10 failed launches if it had not been successfully launched in the last day.

Orchestrator has a “Circuit breaker” policy - it disables schedules that are failing consecutively multiple times. The rule is ten consecutive failures in 24 hours.

It is not possible to disable this behavior per tenant.

• “User System Administrator deactivated the trigger. The “System Administrator” is not an actual user. It’s Orchestrator itself that disables the schedule.

Note: Schedule failing means a failure related to queue / create the job, not the job execution failure itself. For example, licensing issues (not enough licenses), there are no Robots available to schedule, or there are already pending jobs created by the same schedule that have not started execution yet, the Robot is disconnected for more than 24 hours that will lead to “circuit breaker” rule, etc.

Check if the trigger gets automatically disabled at a specific date and time. Perform the following,

1. Click the corresponding Edit button.
2. Uncheck the Disable Trigger at option.
3. Click Update for the changes to take effect.

Check the documentation Managing Triggers.

1. If the schedule is set to run every 15 minutes and if the job itself is taking too long to execute, whenever a new job has to run for this trigger, if the previous job was not finished, this indeed counts as a failure.
2. When the trigger fails too many times, it gets automatically disabled by the system.
3. Check the audit, besides the alert when the trigger gets disabled, lot of alerts about jobs that did not run and a more verbose message with the reason will be available.
4. If the jobs are long running, try to set the trigger to allow more pending jobs or to schedule it to run less often.