Property reference

`mid.inactivity.timeout.days`

Sets the global inactivity timeout, in days, before MID Server authentication expires. The default is 30 days when no timeout is specified, and individual MID Servers can use a different value or disable governance with a timeout of 0.

Default: Not set
Type: Not stated
Application: Not stated
Category: CMDB & Discovery

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	Specifies the global number of inactive days before MID Server Governance expires authentication and invalidates a MID Server, unless a MID Server-specific timeout overrides it.
What area does it affect?	MID Server Governance
What does the default mean?	No out of the box record exists and the scripts that read it pass no fallback value.
When should you review it?	Review when changing the global inactivity period or aligning MID Server authentication expiry with operational requirements.

Property record

No out of the box record exists. ServiceNow scripts read this property; create it to change the behavior.

Property name	`mid.inactivity.timeout.days`
Type	Not stated
Application	Not stated
Default value	Not set
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... MID Servers by setting the following true/false system property: mid.inactivity.timeout.enabled. This property is not defined by default. The global inactivity timeout is specified by setting the following integer system property: mid.inactivity.timeout.days. The property takes an integer which specifies the timeout in days. The default timeout is 30 days if unspecified. You can override the timeout for a particular MID Server by ...

Used in

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.

Business rule: MID Server Auto Invalidate Notification The notification rule reads this property as a fallback when the MID Server’s configured inactivity period is missing or invalid; it sets how many days of inactivity trigger automatic invalidation. If the property is missing or is not a non-negative whole number, the rule uses 30 days. /sys_script.do?sys_id=87986c155bb1701005036e8a1d81c7c6

More in `mid`

Other properties in the same namespace.

mid.em.snmp_old_key_counter_cut.enabled This property enables the removal of trailing OID counter values from translated OIDs to improve event rule… mid.gcp_resource_inventory_bucketpath This property defines the complete file path of the GCP storage bucket used for discovering resources in… mid.gcp_resource_inventory_bucketpath.default This property sets the default bucket URI for GCP asset inventory, enabling automated discovery of resources… mid.hla.itom_gateway_streaming.enabled This property enables MID Servers to stream log data directly to the ITOM Gateway, facilitating real-time… mid.inactivity.timeout.enabled It enables governance checks on MID Servers by enforcing an inactivity timeout, reducing the risk of… mid.install_server.base_uri This property sets the Base URI used by the mid server to download packages, allowing for customization of… mid.jdbc.datastream.max.record.size This property limits the size of records processed by the MID Server's JDBC data stream, with a default… mid.keystore.max_backups This property determines how many key store backups can be retained, with a default limit of three backups.

All 69 properties in mid →