Question
British Telecom
GB
Last activity: 11 Oct 2017 6:35 EDT
Report Schedule Tasks running multiple times
There are few report schedules which are running multiple times (sending out emails many times) and we are unable to debug and understand why. In an attempt to fix this, we have deleted the schedule, ensured there are no stale queue items in SLA and Schedule task table, removed all stale assignments created by old Schedule Task (PX-ST-**) and created a fresh schedule, but for some reason, few of the report schedule task run in loop multiple times. Often these are from a previous day. For example, Today's run will send not just the report from today but also 20+ emails from yesterday. This becomes a recursive event which we have to stop by deleting the schedule item. We are unable to guess why the same report schedule would run for 2 different days, one being from today (as expected) and recursively from yesterday or even 2 days back dated report. One thing noteworthy is these reports are very heavy on performance, not much optimized, so DB timeout exception could be seen in logs and alerts. Need some expert opinion of this issue and direction on how to fix this.
There are few report schedules which are running multiple times (sending out emails many times) and we are unable to debug and understand why. In an attempt to fix this, we have deleted the schedule, ensured there are no stale queue items in SLA and Schedule task table, removed all stale assignments created by old Schedule Task (PX-ST-**) and created a fresh schedule, but for some reason, few of the report schedule task run in loop multiple times. Often these are from a previous day. For example, Today's run will send not just the report from today but also 20+ emails from yesterday. This becomes a recursive event which we have to stop by deleting the schedule item. We are unable to guess why the same report schedule would run for 2 different days, one being from today (as expected) and recursively from yesterday or even 2 days back dated report. One thing noteworthy is these reports are very heavy on performance, not much optimized, so DB timeout exception could be seen in logs and alerts. Need some expert opinion of this issue and direction on how to fix this.
My understanding, which can be wrong, is that once schedule kicks in, it fails to complete in stipulated time, when DB time out occurs, and at certain point the report schedule fires up again considering it never run for the day. This is when it keeps on trying again and again until we manually stop the Task scheduler agent or delete the queue item and schedule task. How do we fix these?Report Schedule Tasks running multiple times