Errors related to offline geocoding can be complex when the connection has dropped. Errors are generated from different locations:
A dropped connection produces a different kind of error - for example, AspNetCore produces a WinHttpException
when a connection is dropped using HttpClient. Your task is to identify how the operating system or programming language exposes a connection error. Once you have identified this error, your code must trap the exception, ensure that you can respond correctly, and prevent the exception from being exposed to the end user or calling system.