Auto-Assignment timeout setting
The performance of Auto-Assignment is influenced by the timeout settings configured for database queries, job scheduler tasks, and the Auto-Assignment process itself. A timeout refers to the maximum time allowed for the Auto-Assignment engine to solve the scheduling problem and generate an optimized schedule. Adjusting these settings can significantly affect the scheduling outcomes.
For example, you can increase the Auto-Assignment timeout to give the optimization engine more time to search for the best possible schedule. This might improve the schedule’s quality or coverage, but the benefits are minimal and may cause delays. On the other hand, shorter timeouts are suitable for simpler schedules with lower staffing requirements, helping to reduce processing delays.
By default, the Auto-Assignment timeout is set to 3 minutes, but you can configure it for up to 10 minutes. When the timeout threshold approaches, users receive warning messages through work mail, alerting them to potential delays or interruptions in scheduling tasks. Configuring the timeout settings correctly is important, as incorrect configurations may cause the Auto-Assignment process to fail.
For example, if the job scheduler task timeout is not long enough, job scheduler tasks could timeout before the optimization engine is finished processing an Auto-Assignment run.
| Registry Parameter | Function | Recommendation |
|---|---|---|
| AS_TIMEOUT_SECONDS | Determines the length of time that an Auto-Assignment process can run on the optimization engine. | By default, the Auto-Assignment timeout is set to 3 minutes or 180 seconds, but you can configure it up to a maximum of 10 minutes or 600 seconds. |
| TASK_TIMEOUT | This parameter specifies the rate at which job scheduler tasks must produce a heartbeat before being stopped by the job scheduler. | Should be set to at least 15 minutes longer than the AS_TIMEOUT_SECONDS registry parameter. For example, if AS_TIMEOUT_SECONDS is set to 3600 seconds (60 minutes or 3600000 milliseconds), TASK_TIMEOUT should be set to at least 4500000 milliseconds (75 minutes). |
| COMMIT_ROLLBACK_SEGMENT_TIMEOUT | This parameter prevents long running (possibly locking) database transactions from locking up the entire application. | Set to at least 300 seconds. |
| QUERY_TIMEOUT | This parameter is used to specify the length of time to wait before timing out any long-running, potentially locking queries with an SQLException being thrown from the database side. | Set to at least 300 seconds. |
For more details, see the Infor WFM Registry Parameter Reference Guide.