mid_server.failover.max_count Limits how many jobs the MID server failover process handles in one pass when a MID server goes down. The default is 25,000 jobs, so raising or lowering the limit changes how much work is processed before failover continues.
DEFAULT_MAX_COUNTThe answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | Sets the maximum number of jobs processed in one pass by MID server failover after a MID server goes down; the default is 25,000. |
|---|---|
| What area does it affect? | MID Server failover |
| What does the default mean? | The default value is "DEFAULT_MAX_COUNT". |
| When should you review it? | Review when adjusting how many jobs failover processes per pass after a MID server goes down. |
No out of the box record exists. ServiceNow scripts read this property and use the default value shown until you create it.
| Property name | mid_server.failover.max_count |
|---|---|
| Type | Not stated |
| Application | Not stated |
| Default value | DEFAULT_MAX_COUNT |
| Description | Not stated |
Official references and nearby text excerpts where this property appears.
Out of the box artefacts that read this property. Append the path to your instance URL to open the record and see how the value is used.
/sysevent_script_action.do?sys_id=f6c24d230a0006bc394931345fba7a8a
mid_serverOther properties in the same namespace.
mid_server.cluster.debug
This property activates detailed logging for the MID server cluster, helping to diagnose issues or monitor…
mid_server.failover.debug
When enabled, records debug messages generated during MID server failover in the system log.
mid_server.failover.query_window
Sets the duration, in days, of the query window used during MID Server failover.
mid_server.failover.total_max_count
Sets the total record limit used during MID Server failover, with a fallback limit of 1,000,000 records when…