Too many database calls

Way too many database calls. This is happening on every endpoint, but I'm using /validate_token as an example. Is this the expected behaviour to make 3 database calls just to fetch the user?

Those many database calls lead to other issues, for example, 500 error responses because user table is locked

Start by tracing the /validate_token endpoint and counting its database calls, with particular attention to fetching the user and the user table lock mentioned in the report. Done means the endpoint no longer makes unnecessary calls and avoids the reported 500 responses caused by locking.

Written by the indexing model from the issue text.