You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging biosecurity alerts, the tomcat logs often show failed requests to Biocache. This is often due to a incorrect custom fq param in the biosecurity list data or is caused by a WKT polygon that is too long. The logs show the biocache query but there is no way to know which species list was being processed, when the error occurred.
include the list DR (optionally include list name) in the error log when calling external REST APIs.
E.g. this call is an example where the list DR should be included. But there are many more instances that require fixing.
The text was updated successfully, but these errors were encountered:
When debugging biosecurity alerts, the tomcat logs often show failed requests to Biocache. This is often due to a incorrect custom
fq
param in the biosecurity list data or is caused by a WKT polygon that is too long. The logs show the biocache query but there is no way to know which species list was being processed, when the error occurred.E.g. this call is an example where the list DR should be included. But there are many more instances that require fixing.
The text was updated successfully, but these errors were encountered: