My Annotations email being sent even when no updates

[kylie-m]

At least one ALA user has reported receiving the same My Annotations alert email daily - Sometimes every day for a while, at other times at intervals of a month or so.

• It appears that there are records being included that have not been updated that day. ie. same record in 20 days worth of emails
• The records may be being re-loaded with data updates, especially for iNat and museum records

I have forwarded an example email, but am happy to continue testing and narrowing down the issue.

Freshdesk ref: https://support.ehelp.edu.au/a/tickets/220936

[kylie-m]

Tagging @adam-collins also as you may have insight into this too

[qifeng-bai]

@kylie-m and I checked the DB. The'Current' check happened on

| last_checked | previous_check |
+---------------------+---------------------+
| 2024-12-19 08:30:37 | 2024-12-18 08:30:29 |

Last check result contains 151 records - which is correct. the previous_check result happened on 18/12 does not have any records - which is Odd since it should has some records, unless all 151 records were updated after 18/12

We ran a dry-run, no error was found, and the result is as expected - the current result matches the previous result in database. Therefore we would expect an alert would not be triggered.

And then we manually trigger this alerts, alerts did not find any new records, so email was not sent.

[qifeng-bai]

And I have checked the Prod db

 mysql> select * from property_path where query_id=2194;
Empty set (0.00 sec)

The diffService will do Full comparison to find new records. Arthur should not get repeated emails which contain 151 records. The reason why Arthur got the email on 19/Dec is that the previous_result in DB was empty, which we do not know the reason yet.

[peggynewman]

What date in biocache is being used to check the data? first load date or last load date?

[qifeng-bai]

@peggynewman first load date
'firstLoadedDate:[' + utcFrom + ' TO ' + utcTo + ' ]'

[kylie-m]

Change to behaviour in next alerts release should fix this - see #346