sorry for the late reply on this.
this is really interesting. this is an interesting sql being created by the DB-driver (originating from
In general, the AP scans sequential. there is no parallel processing so I have no clue where this issue comes from.
My only Idea would be that your database had a temporary load issue and was not finished with the write itself (or the update of the index) when the next came in.
its hard to clarify. but if your issue is solved (it would also be solved by pressing “Scan” again in the frontend, I guess), I would leave it there for now.
if you have this coming up again, please let me know.
thank you for your feedback…