Property reference

com.glide.update_operation.max_failure_count

The com.glide.update_operation.max_failure_count property sets the maximum number of times an operation can fail before it is removed from the queue. Administrators should adjust this value to manage how many retry attempts are allowed for failed application package downloads or resource checks.

Default
Not stated
Type
Not stated
Application
Not stated

Key questions about this property

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

What does it do? This property determines the threshold for failure attempts before a queued job is discarded, specifically for errors related to downloading application packages.
What area does it affect? Application Operations Queue
What does the default mean? No default value is stated in the ServiceNow documentation.
When should you review it? Review this property when configuring application deployment settings or troubleshooting failed operations.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name com.glide.update_operation.max_failure_count
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
... a determined number of times, the tracker fails, and the job is removed from the queue. The maximum number of times defaults to 3 and can be modified by the com.glide.update_operation.max_failure_count property. Note: Failing to obtain necessary locks doesn't count as a failure attempt. Only errors encountered such as failing to download an application package from AppRepo count. Custom licensing for ...

More in com.glide

Other properties in the same namespace.

All 831 properties in com.glide →