Overview
Parameters:AUTOCHANGESTATEBATCHSIZE
Category: Workflow
Default value: 1000
Product: eTASK.Workflow
What does this parameter do?
This parameter controls how many tickets are retrieved and processed simultaneously by the "GlWorkflowStepFollowSwitch" timer job per run. The timer job is responsible for automatically advancing tickets in workflows when certain conditions are met. By specifying the batch size, you can control the processing speed and system load.
What is this parameter used for?
Controlling the number of tickets processed per timer job run
Performance optimization during automatic workflow processing
Conserving resources during high system load
Preventing timeouts during workflow processing
Balancing processing speed and system load
Technical Details (for Administrators)
Format: Integer
Default value: 1000
Valid values:
10= Minimum batch size (very resource-efficient, slow processing)100= Small batch size (resource-efficient)500= Medium batch size (balanced)1000= Standard batch size (recommended for normal systems)2000+= Large batch size (fast processing, higher system load)
Important notes:
The value determines the page size for the database query
The timer job processes tickets in batches until all relevant tickets have been processed
With very large values, the job may run longer than the recommended 5 minutes
Values that are too small may result in tickets not being processed in a timely manner
In debug mode, the value is automatically set to 10
The job processes only tickets in active workflows with automatic switching enabled
Interaction with other parameters:
This parameter works in conjunction with the "GlWorkflowStepFollowSwitch" timer job, which runs at regular intervals and automatically advances tickets in the workflow.
When should you change this value?
Decrease the value (e.g., to 100–500) if:
The timer job runs for longer than 5 minutes
The system load is too high during job execution
Database timeouts occur
You want to conserve resources
Many other computationally intensive processes are running simultaneously
Increase the value (e.g., to 2000–5000) if:
You have many tickets that need to be processed automatically
The timer job is running too slowly and tickets are piling up
Sufficient system resources are available
You want to reduce the processing time
You have a high-performance system with a good database connection
Important Notes
Monitoring the job runtime
Monitor the runtime of the "GlWorkflowStepFollowSwitch" timer job. If it regularly runs for longer than 5 minutes, you should reduce the value.Balance between speed and system load
A higher value leads to faster processing, but also to higher system load. Find the optimal value for your system environment.Impact on ticket processing
With very low values, tickets that need to be processed may remain pending longer because other tickets are blocking the process.Test after changes
Change the value incrementally and monitor the effects on job runtime and system load over several days.
Security
Does changing this parameter affect security?
No, this parameter has no direct security implications. It is a performance parameter designed to optimize workflow processing.
Note: * Values that are too high can lead to system overload * Values that are too low can lead to delayed ticket processing * Indirect impact on service level agreements due to delayed processing is possible
Recommendation: Choose a balanced value that enables fast processing without overloading the system. Monitor job performance regularly.
Practical example
Initial situation: Your system automatically processes several hundred tickets daily via workflows. The "GlWorkflowStepFollowSwitch" timer job runs every 5 minutes, but has recently been taking longer and longer to complete, sometimes exceeding the 5-minute limit. This leads to overlaps and increased system load.
Configuration: AUTOCHANGESTATEBATCHSIZE = 500 (reduced from 1000)
After the change:
The timer job now retrieves only 500 tickets per run instead of 1000
The database query runs faster
The processing time per job run drops to 3–4 minutes
The system load during job execution is lower
Tickets continue to be processed promptly, as the job runs every 5 minutes
Result: The timer job runs stably within the 5-minute limit. The system load is distributed more evenly. All tickets continue to be forwarded automatically in the workflow in a timely manner without any delays.
Alternative scenarios:
Scenario A - High-performance system with many tickets:
AUTOCHANGESTATEBATCHSIZE =
2000Faster processing of large ticket volumes
System has sufficient resources for large batches
Scenario B - Weaker system or high overall load:
AUTOCHANGESTATEBATCHSIZE =
250Very gentle processing
Longer total processing time, but no system overload
Recommended setting
For standard installations:1000(Default)
Reason:
Proven value for most system environments
Good balance between processing speed and system load
Sufficient for typical ticket volumes
Tried-and-true default value with good performance
Exceptions (adjustments):
Small systems or high overall load: Reduce value to 250–500
Large, high-performance systems: Increase value to 1500–2500
Very many automatic workflows: Optimize value individually
Job runtime exceeds 5 minutes: Reduce gradually (e.g., to 750, then 500)
notecfcf289a-89ad-451b-a40d-ee902d5f5a61
Tip: Start with the default value of 1000. Monitor the job runtime in the timer job logs. If the job regularly runs longer than 5 minutes, reduce the value in increments of 250 until the runtime is consistently under 5 minutes. If you have many tickets and need faster processing, increase the value gradually and monitor the system load.
Tip: Start with the default value of 1000. Monitor the job runtime in the timer job logs. If the job regularly runs for longer than 5 minutes, reduce the value in increments of 250 until the runtime is consistently under 5 minutes. If you have many tickets and need faster processing, increase the value gradually and monitor the system load.