I have some users testing stuff on my site at the moment and I wanted a way of auto-publishing all their test assets a short while after they created them. So I've added a trigger on the event "asset created", critera of the root node and the asset types I want. In the action I have just one thing "Set Future Status". Its set to "immediately" with an offset of 10 minutes.
The cron jobs get created, and most of the time they run OK and the asset gets made live. But about 30% of the time, the cron job stays in the queue and doesnt run, and the asset stays in pending status.
If I look at the cron jobs screen, it shows the jobs there, with the run time clearly in the past. If I look at the asset details, that shows an entry for "Scheduled future status changes" but again the "when" is clearly in the past.
Any ideas what could be causing the jobs to get missed?
Cron jobs to set future status not running reliably
Anthony
(Anthony)
#1
LightningMcQueen
(Tim Mcqueen)
#2
I assume the accounts have the relevant permissions for the 30% that fail?
(I believe this can be overridden with the Trigger settings also.)
Is there any messages in your Error Log (under System Management --> Log Manager) ?
coolwebs
(Ryan Archer)
#4
I am experiencing a similar issue right now and when I looked a the error log (Log Manager) for cron jobs it says thatÂ
[2015-04-02 01:00:29][482:Steve Scamp][512:mysource warning][R] (/core/include/locale_manager.inc:547) - You do not have permission to save the attributes of "Regenerate "Links report - SLQ main site" [#278012]" (#278679) [CORE0121]
This happened on the 2nd April 2015 and no cron jobs have run since then. How would I fix the cron manager by enabling the permission to save the attributes of the asset?