No problem @Oleksandr_Dovgopol,
We have an engineering investigating this. The engineering manager told me that it would not be possible to turn this off. But that they did see some occasional spikes in load times of the endpoint.
With your query run time being a major outlier but seen not the only one. Hopefully the issue is an N+1 condition in the search algorithm that finds the current users data which the endpoint returns and it can be patched quickly.
For added context, even if you aren't using{{current_user}} in the app, the org needs to grab the user's data to understand what permission groups they belong to for the app to work ![]()