Currently, when a mobile or reactive app client disconnects mid-request (e.g. user backgrounds the app, loses network, or a timeout occurs), OutSystems logs the following errors in Service Center as 500-level errors:

• "The client is disconnected because the underlying request has been completed. There is no longer an HttpContext available."
• "Failed to send request due to unexpected error"

These errors are thrown deep in the ASP.NET/IIS pipeline by the ErrorNotifierModule, below the OutSystems application layer. This means developers have no way to catch or suppress them using OutSystems logic — not through OnException handlers, not through error handling in Client/Screen/Data Actions, and not through any pattern available in Service Studio.

Why this is a problem:

• These errors are not actionable by developers — there is no OutSystems-level fix that prevents them
• They pollute the error log in Service Center, making it harder to identify real application errors (we currently have an average of 60.000 daily errors like these)
• They generate false alerts in monitoring tools and APM integrations that consume OutSystems error logs
• They cause unnecessary noise in production environments, particularly for mobile apps used on unreliable network connections

What we are asking for:

OutSystems R&D to implement one or both of the following:

1. Suppress specific known client-disconnect exception types (e.g. HttpException with error code 0x800703E3) in the ErrorNotifierModule before they are written to the error log, since these represent expected network-level events, not application bugs
2. Provide a configurable filter mechanism in Service Center or Factory Configuration that allows platform administrators to define error message patterns that should be downgraded (e.g. to a warning) or excluded from the error log entirely

Expected outcome:

Developers and operations teams can maintain clean, actionable error logs that reflect real application problems — without being forced to implement infrastructure-level workarounds outside the OutSystems platform.