We found certain queries coming from clients and timers get stuck in IIS indefinitely, despite having timeouts. These queries were sitting in IIS without any way to know this until our environment was inaccessible and we had to reach out to support to resolve the issue. While this clearly is a bug, support stated they would not be resolving this issue and thus we should create an 'idea' for it. Truthfully, not an idea, a bug that needs to be resolved because it results in OutSystems environments slowing down over time, eventually leading to them becoming inaccessible, and customers don't have visibility into IIS.

Additionally, as part of my 'idea', I would suggest the OutSystems website to reflect the fact that this can happen as statements like "Every web request done to an OutSystems application takes its time to process by the application server (IIS) and is ruled by a Request Timeout that prevents the existence of everlasting web requests", are false. Obviously such a change would only be necessary in the short term as ideally, this issue would be resolved, but until then statements of this sort on their website are lies.