Maybe your server just timed out. If you have scheduled with wget commands (like suggested somewhere in the documentation/how-tos), these requests will time out the same way as default requests you run on your server. You can try that by running the jobs URL manually from your browser and see whether it gives you this error "Maximum execution time of X seconds exceeded in..."

Other possibility is that it reached memory limit but you should also see this by running the jobs manually.

I believe it is not running anymore, it probably didn't just reach the final step where the status of the job is updated. This is also why the interface where you see the jobs would tell you it's still running.

Did you ever work this out?

I have the same issue and the site is currently a local MAMP install - just spins continuously since 5.6 update.

Seehttp://www.concrete5.org/community/forums/customizing_c5/index-sear...