Hi Will:

The short answer is that we have not seen this reported as a common issue in upgrading to 23.7.0 in the Community Edition, and offhand nothing looks amiss in your environment. A few ideas:

1. Have you checked out the rest of the log to see if there is something happening upstream of this exception?
2. Since it looks this could be related to indexing, were you running these jobs immediately after the upgrade when perhaps an overall reindexing was happening at the same time?
3. Is it consistent and have you isolated it to be only happening during deletion? i.e. does a version where you do the queries but not the deletion run successfully? Watching the query profiler might also provide hints?

--Molly