Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
Sets the maximum time, in milliseconds, that a MID Server can spend processing a cloud REST request during discovery. |
| What area does it affect? |
MID Server cloud discovery |
| What does the default mean? |
No default value is stated in the ServiceNow documentation. |
| When should you review it? |
Review after discovery fails with a REST timeout, especially when many configuration items return large responses. |
Property record
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name |
mid.sa.cloud.request_timeout |
| Type |
Not stated |
| Application |
Not stated |
| Default value |
Not stated |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... timeout. There are many CIs sending the REST call response in the deployment. The MID Server cannot process the REST call response without exceeding the time limit controlled by the mid.sa.cloud.request_timeout parameter. By default, the mid.sa.cloud.request_timeout parameter is set to 30000 milliseconds. Increase the value of this parameter on the relevant MID Server and run discovery again. Note: If the Configuration ...
Context preview
Snippet 2
... access the ServiceNow instance, and the proxy requires a user name, set this parameter to define that user name. • Type: string • Default value: none Request timeout override parameters mid.sa.cloud.request_timeout Sets the timeout in milliseconds for cloud requests. This parameter overrides the glide.http.timeout system property, which specifies the maximum number of milliseconds to wait before an outbound REST transaction times ...
More in mid
Other properties in the same namespace.
All 257 properties in mid →