Biosecurity alerts - cancel a running job if biocache errors occur

[nickdos]

This week's scheduled biosecurity job failed due to DB connection errors:

org.springframework.transaction.TransactionSystemException: Could not roll back Hibernate transaction; nested exception is org.hibernate.TransactionException: Unable to rollback against JDBC Connection

Best guess is that this was a result of the preceding Biocache errors (504 Gateway Time-out), that were caused by "bad" fq queries from one of the lists (used a spatialObject that was too complex).

• When a biosecurity job encounters an error from Biocache, it should fail and log the reason and then move to the next job

[nickdos]

Instead of sending an email on failure, could we add a flag on the alert entry in the DB, indicating the last job failed. Then show that flag on the biosecurity admin page, next to the alert?