If your scheduled tasks aren't working
 

I have seen some problems over at vbulletin.com about some scheduled tasks not running. Here is one possible fix.

If you are running an upgraded board, go to your scheduled tasks manager. Remove any scheduled tasks that are not installed by jelsoft and were not installed with a 3.5 modification.

The default ones that come with vbulletin are:
Daily Digest
Subscriptions
Daily Statistics Log
Event Reminder
Thread Views 07-10-2005
Hourly Cleanup #1
Attachment Views
Restore Temporarily Banned Users
Hourly Cleanup
User Promotions
Weekly Digest
Happy Birthday Email

One 3.5 mod I know of that adds one is my Velocity Modification.

If you are a 3.5 mod author and have created a mod that has an updated scheduled task, please let me know and I shall add it to this list.

I don't have any added, but mine still aren't working.

I went through and saved each of them, which put them back to current 'next run time' but they didn't run as scheduled.

I wonder if there is a mismatch on the cron image vs what is being called? Haven't looked though.

vBouncer introduces 2 cron tasks, in 3.0.7 and in the 3.5 version.

vBouncer Clean
vBouncer Collect

If you have problems with cron jobs not running, the first you could try is reverting your footer template.

Did that. The scheduled task functions are running. The nextrun time is being updated and all that. It's just not running the actual code that it should run. BUT some tasks do work.

Is this a 3.5 specific thing you are talking about? I do know that in 3.0 the cron handling got it's own strange things, for example in handling global variables.

Amy, the tasks that fail to run by cron, do they actually run from the scheculed task manager by clicking "run now"?

Yes. They do, Tamarian.

O.k. I think I've seen this before, the task runs from the rask manager, but fails to run as a cron.

Does the failed cron task file contain any function declaration(s)? If so, removing those functions and opting for a single block of code fixes this.

I had the same problem with my Thread of the Week hack for 3.0.7.

If you use a global variable inside a function, things work strange. Best to pass all used variables as parameters to the functions.