I would need more time for an analysis,

but the standard idea would be to make the path-to-solution explicit, verifiable ("also tell us how you got to that"). In other terms, "avoid the black box". Maybe have the generated SQL query output... But this will not impede abuse from lazy users, and errors "may have consequences".

Databases (just think of the testing infrastructure for SQLite) are made to be fully reliable; if the interface were not so, you would have broken the model.

Yes, that was what we were thinking about when starting but we didn't want users to abuse our service.

However, I'm sure that we'll find a solution soon enough.

Issue is, you need not mitigation but certainty (for normal database operation).

The quickest path could be having a testing environment set to determine a tentative value for your failure rate, declaring it to the public and declaring in your disclaimer the scope of the your product.

Yes, we'll do this