Since the upgrade to 2.3 a month ago I've got the notice about outstanding manual jobs in ACP:
I assume that these are template rebuilds since these take forever (hours) and the web frontend runs into a timeout/deathloop whatever w/o ever reaching a "finished" notice. That happens reliably when I click on "continue running them".
The reason might be that I am on shared hosting and possibly the runtime of scripts is too limited to complete these jobs. However: This has never been a problem on 2.2, it only started with the 2.3 upgrade and went competlely bonkers when importing a language.
I've thus logged in via ssh and run the jobs manually. However: The system states everything would be fine:
$ php cmd.php xf:run-jobs -vv
All outstanding jobs have run.
This result comes instantly, so it does not seem that the CLI would have run any job and the notice in ACP persists. Is there a way to find out which jobs exactly are outstanding and a way to make these run decidatedly?
I assume that these are template rebuilds since these take forever (hours) and the web frontend runs into a timeout/deathloop whatever w/o ever reaching a "finished" notice. That happens reliably when I click on "continue running them".
The reason might be that I am on shared hosting and possibly the runtime of scripts is too limited to complete these jobs. However: This has never been a problem on 2.2, it only started with the 2.3 upgrade and went competlely bonkers when importing a language.
I've thus logged in via ssh and run the jobs manually. However: The system states everything would be fine:
$ php cmd.php xf:run-jobs -vv
All outstanding jobs have run.
This result comes instantly, so it does not seem that the CLI would have run any job and the notice in ACP persists. Is there a way to find out which jobs exactly are outstanding and a way to make these run decidatedly?
