When submitting a sighting for testing purposes, I often will delete it quickly.
It appears that what happens in this case is that the delete operation
completes before the job that syncs the sighting to ALA can run. The job then
gets stuck attempting to query the record (which no longer exists).
Probably the delete operation should delete any outstanding create/update jobs
or the create/update job has to handle the case where the sighting record no
longer exists.
Original issue reported on code.google.com by chris.go...@gmail.com on 13 Jan 2014 at 10:38
Original issue reported on code.google.com by
chris.go...@gmail.com
on 13 Jan 2014 at 10:38