Scheduled tasks do not run correctly

[Segi]

I have a total of about 20 different scheduled tasks that send out email reports and our end users are telling me that they are getting reports at the wrong frequency.

I compared the schedule frequency for each scheduled task and compared that to the scheduled task logs and found many discrepancies.

For example, I have a few tasks that are scheduled to run every working day at 8 AM. In the task logs, these tasks show that they have triggered every day including weekends.

Tasks that are supposed to run weekly on every Friday seem to execute on Friday and Saturday of each week.

Another tasks that is set to execute every 8 hours (This tasks runs a database update command but doesn't send out an email report) has been executing every hour.

I have another task that is set to run daily at 5:30 AM and this task appears to execute exactly when it should.

Another weekly task is executing daily instead of weekly.

I am waiting for the right opportunity to restart the server to see if the schedules correctly trigger when they should but this is a serious bug.

[Jon]

Thanks for reporting this. We will investigate.

[Jon]

This has been partially fixed in V5.1. Unfortunately there wasn't time to do more than that before the cut-off for release. The cost of the "partial fix" is that the next execution date for a scheduled task is only calculated each time it executes e.g. if you change a task from monthly to daily, this change won't be evaluated until the task next runs.

[Segi]

Jon

what about between server restarts ? Will restarting the server force the next execution time to be re-evaluated ?

[Jon]

No, afraid not.

[Segi]

Jon,

I am on 5.1.1 now and recreated all of my scheduled tasks after upgrading to 5.1.1.

I have just finished checking the scheduled tasks log. Almost all of my scheduled tasks run correctly except those that are specified to run every working day.

Tasks that are scheduled to run every working day are running every day including weekends. I'd appreciate if you guys can look into this and fix this in the next release of Ebase.


thanks,

Segi

[Jon]

OK, thanks for the update, we'll look at it.