Property reference

com.glide.system_parallel_job_inactive_time_minutes

The com.glide.system_parallel_job_inactive_time_minutes property sets the maximum duration a parallel job can remain in a running state before being marked as pending. Admins should review this setting to manage job processing times and prevent delays in data imports.

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 defines the timeout period for parallel jobs, determining how long they can run before being automatically reset to a pending state.
What area does it affect? Parallel Job Processing
What does the default mean? No default value is stated in the ServiceNow documentation.
When should you review it? Review this property when configuring import job settings or troubleshooting job delays.

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.system_parallel_job_inactive_time_minutes
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
... minutes, it's automatically put back into a Pending state. You can modify the amount of time a parallel job is allowed to be stuck in a running state with the com.glide.system_parallel_job_inactive_time_minutes property. If a parallel job can't complete after two tries, the job is set to Error. You can modify the number of tries before having an error state with the ...

More in com.glide

Other properties in the same namespace.

All 831 properties in com.glide →