Comment 3 for bug 1549947

I have something to add to Allie's feature request: there may need to be some changes to the "export_process_queue" CRON task that archives submissions before they are released.

All of our courses (groups) are configured to archive submissions before release, so while the export_process_queue CRON task was processing about 150 collections (600 pages), PHP encountered a max_run_time error, and stopped the task partway through, so some were archived, but none were released.

The export_process_queue task locks itself when it starts and cannot be run again until it has finished, but if it crashes it does not unlock.

So for about 36 hours after this task crashed, anything that was flagged for release just said "Pending release after archiving" and nothing happened. I had to go into the config table in the database and deleted the lock, and clear out the export queue.

So this potential error will need to be handled in some way, otherwise it will probably happen a lot more often if an entire class can be flagged for archiving & release all at once. 150 collections was only 1/4 of the class.