Developer forum

Hi Igor,

In situations when screens have that much database activity, this error is expected. However, you're only seeing it because you're logged in as Angel. It's meant for internal diagnostics and performance troubleshooting, and therefore not something that anyone outside the organization would ever see. That's also why the error is as annoying as it is. As a workaround, you can log in as a different user.

I cannot say why you're getting that many requests to the database in the first place, but you can try to attach a SQL Profiler and see if it's actually the case and, if it is, what those queries are. Perhaps that can give you an idea of why it happens.

- Jeppe

Hi Jeppe,

An opt out option for my Angel user would be appricated. I can ofc go in and debug why I am getting the error, but I am not doing diagnostics or debugging at the moment, I just want to view some product data in the back end of my local solution

Then you need to use a different user than Angel for the moment, I'm afraid. To my knowledge, it's not a general issue, rather it seems to be specific to your solution, so it needs to be investigated why you're experiencing this.

I don't think we'll make an override to turn this off as the idea is that no screen should ever produce that much activity, and this was made as a blocker to avoid pushing badly performing screens to release. It's not my decision though.

In any case, I don't think this is a discussion to have on the forum as it's purely an internal issue.

- Jeppe