30 views

Description

Workflow set on the sc_request table seems to hang intermittently on the first-timer of 10's.

Managed to get it started by updating the REQ itself, the restart hung workflow did not work.

Release or Environment

ALL

Cause

ASYNC Business Rules

Resolution

- The system does not allow the WFTimer jobs to be pushed ahead of ASYNC jobs, and vice-versa. This causes delay in WFTimer jobs while waiting on the worker threads.
- Open the System Diagnostics page and check the scheduler queue length. In these circumstances, if the value shows in red, the scheduler is overloaded. Check all active ASYNC Business Rules generating scheduled jobs that are flooding the scheduler. Disable Async Business Rules, review and evaluate why the scheduler cannot handle the intended load.
- For the priority level issue of the timer activity, a business rule can be created on the sys trigger table that will check to see if a wf.timer record is inserted. Once it gets inserted, the business rule should change the priority value to 90.
- All jobs on the sys_trigger table run at a priority 100. Therefore, making the wf.timer priority to 90 will cause it to run before other scheduled jobs, which will fix the issue.


Article Information

Last Updated:2020-03-15 00:22:10
Published:2020-03-15