Is it really necessary to load each nodes on every cron job. Because query selects All expired nodes, and it`s may be a big amount of nodes.

May be we can use just 'nid' for Rules, and than each function can load node if necessary ?

Or add some hook to check if we really want to load or skip this node ?

Comments

magpie5212’s picture

Not sure of the solution, but I think I am suffering this. When I have the 'content expired' rule enabled in the Triggered Rules the cron fails the first time with a '500' type server error - effectively too much being run.

Nafes’s picture

The solution is going to be released soon. See here at #1774402: Allow cron to trigger "Content Expired" rule only once.

Nafes’s picture

Version: 6.x-2.x-dev » 7.x-1.x-dev
Assigned: Unassigned » Nafes
Issue summary: View changes
Status: Active » Reviewed & tested by the community
Nafes’s picture

Fixed in 7.x-1.0-alpha3.

Nafes’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.