Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
It sets an integer limit on how many instances of the same Discovery schedule can run simultaneously, helping to manage system resources effectively. |
| What area does it affect? |
Discovery scheduling |
| What does the default mean? |
The default value is "3", which sets the baseline numeric behavior for this property. |
| When should you review it? |
Review this property when adjusting Discovery schedules or troubleshooting performance issues. |
Out of the box property record
Raw metadata from the property record.
| Property name |
glide.discovery.max_concurrent_invocations_per_schedule |
| Sys ID |
4adc58b24722210003d79da33ede27c6 |
| Type |
integer |
| Application |
Global |
| Default value |
3 |
| Description |
<b>Maximum concurrent invocations per schedule:</b> Prevents an unbounded number of invocations from inundating the system when a schedule takes longer than the time between invocations. The value is an integer defining the maximum number of automated invocations of the same schedule that may proceed at one time. If the limit has been reached subsequent scheduled invocations will be cancelled. The default value is 3. A value of 0 or any negative number will disable this restriction. |
| Updated |
2014-10-23 16:32:38 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... to true, the ESX Servers are marked as absent instead of retired if the ESX server isn’t found in the payload. • Type: true | false • Default value: false glide.discovery.max_concurrent_invocations_per_schedule Maximum concurrent invocations per schedule: Prevents an unbounded number of invocations from inundating the system when a schedule takes longer than the time between invocations. The value is an integer ...