maximum runbooks

Question

Hi :)

At a customer we have a lot of events telling us "the number of runbooks on the runbook server is approaching the maximum number allowed for this runbook server" which is, in our case, 200.
when I take a look with the orchestrator health checker:

As you can see we are not nearly at that amount of running runbooks.

I have no idea where to look or even how to solve this ?? maybe you guys can give me some hints or tips where to start ???

thanks in advanced,
Bart

Answer 1

Hi @Vrakking ,

By default, each Runbook Server is configured to simultaneously run a maximum of 50 runbooks, it appears that you have modified this value, which is OK as long as the server performance allows it.
You might be receiving this event because one of your runook server's runbook usage percentage is "yellow", the 86.50% one.

This is mainly just a warning, nothing to be worried about.

----------

(If the reply was helpful please don't forget to upvote or accept as answer, thank you)

Best regards,
Leon

Answer 2

In addition to LeonLaude:
The 200 runbooks aren't the total of all Runbooks ;-)
It's the total of the "running Runbook instances/jobs".

If the maximum of Runbook jobs is reached (by default 50 in your case 200) the requests to start a runbook will be queued.

More information you could find here:
How Orchestrator processes a runbook
Job concurrency

Regards
Andreas Baumgarten

(Please don't forget to Accept as answer if the reply is helpful)

Answer 3

Hi,
in addition to Leon and Andreas:
Rubook Servers work in failover mode (not load balancing) . A Runbook will be executed on the primary Runbook Server until the maximum number of Runbooks (default: 50, in your case: 200) is reached or the Runbook Server has problems. Then on the secondary, then on secondary(2), ...
The order of the Runbook Servers you can see in Runbook Designer in folder "Runbook Servers".
You can change the Runbook Servers from this order with "Invoke Runbook" Activity or in the properties of each Runbook.

Regards,
Stefan

Answer 4

Hi,

additionally, you said you have 300+ Monitoring Runbooks, that's, as Andreas already said, is the "Problem" that SCO has a limit of 50 actively Running Runbooks.

This limit can be changed, but what i would recommend, to combine your Monitoring Runbooks in one Runbook.

What we do, when we have many Runbokks which should be triggered each hour or each 15 Minutes
We configure one Master Runbook with the Monitor-DatEtime, which will then trigger the Child Runbooks.