Closed (duplicate)
Project:
Scheduler
Version:
7.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Feb 2013 at 14:52 UTC
Updated:
24 Jul 2013 at 16:35 UTC
Jump to comment: Most recent file
Comments
Comment #1
radiobuzzer commentedconsequently I went to the content > scheduled and I saw that there was a task with no node associated , only date was shown. This seemed very suspicious. I therefore went manually to the SQL table 'scheduler' and I looked for the entry around the specified date. Indeed, that was a scheduled task pointing on a deleted node. I deleted this table row and now scheduler works again.
I do not know why this was still in the table, but it was causing failure.
I can recall that this issue starting occurring after the upgrade to drupal 7. The deleted node was entry there from drupal 6.
Perhaps, there should be some function that prevents error from tasks pointing to non-existing nodes.
Comment #2
radiobuzzer commentedHere is the screenshot of the entry with no node attached
Comment #3
jonathan1055 commentedHi radiobuzzer,
Yes you have found a problem here. It will be solved in the same fix as for #2011692: Prevent cron errors when scheduled nodes no longer exist hence closing this issue as a duplicate.
Jonathan
Comment #3.0
jonathan1055 commentedfixed path