XF 2.3 How to identify outstanding jobs?

[smallwheels]

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?

 

[duderuud]

You could check the xf_jobs table in the DB.

 

[dutchbb]

[OzzModz] Job Runner Manager

Oct 1, 2022

Allows to see a list of currently running jobs and manage them

• Painbaker
• Add-ons [2.x]

 

[smallwheels]

You could check the xf_jobs table in the DB.

That was the way. Checked the table, found a bunch of older jobs by add ons, probably caused by the upgrade and uninstallation of add ons when updating to 2.3.8 about a month ago. Made a backup of the db, deleted those older jobs, rebuilt the addons in question just to be sure and everything seems fine now. Notice in ACP is gone and no issues so far.

Did however not find out how I could have ran them - possibly the Job Runner add on could have done it but I had solved the issue before the hint to that was posted.