Some biosecurity alerts not triggered this week

[turley85]

A number of alerts have not triggered this week. For example:

NSW invasive species unit has records:

ISUissue.pdf

But last checked data has not changed (eg. it didnt' trigger today)

This appears to be repeats for at least this list (I'll update as I test more).

1. 7 new records for VIC_Weeds_KB, dr28298 since 16 Oct 2024'

[turley85]

1 new record for NSW_DPI_Marine_list, dr27347 since 16 Oct 2024

[turley85]

42 new records for NSW_LGA_HRCC_Weeds, dr27346 since 16 Oct 2024

[turley85]

1 new record for NSW_DPI_CaneToads_list, dr27345 since 16 Oct 2024

[turley85]

16 new records for AUS_CEBO_list, dr27344 since 16 Oct 2024

[turley85]

2 new records for AUS_ACPPO_list, dr27342 since 16 Oct 2024

[turley85]

23 new records for ACT_Weeds_list, dr27341 since 16 Oct 2024

[turley85]

All those lists above failed to trigger today.

[nickdos]

Hi @turley85 - Bioscurity alerts appear to have failed about half way through. The failure was due to too many database connections timing out, which appears to have been triggered by the "bad" spatialObject queries in the Western Weeds list (as discussed in #319).

In the short-term, I think we need to ensure new lists are first successfully trialled in the alerts-test env. Longer-term, we need to understand why the database errors are occurring and possibly add code to stop any alert from running, if any biocache errors are encountered.

I've created an issue for this (#321), as it has the best chance of preventing future DB errors like we saw this week.