Hmmm… Could be my fault that we don’t see the exception as I don’t try/catch the db operations. In the “tuning process” I have made as much code run in background threads as possible. So I guess an exception from a query in the background could behave like this. Suppose I’ll need to surround all db operations with a try/catch - and then propagate the exception up to MS App.Center if it occurs…
But you also helped by saying that this is not “ordinary” operations - but something more extraordinary going on 