> This page is for Documentation, version Integration guides (default).
> For other versions, use one of these documentation indexes:
> - Integration guides (default): https://avalara.ferndocs.com/docs/integration-guides/llms.txt
> - Refactor guides: https://avalara.ferndocs.com/docs/refactor-guides/llms.txt
> - Get certified: https://avalara.ferndocs.com/docs/get-certified/llms.txt
> - Agent to Agent (A2A): https://avalara.ferndocs.com/docs/agent-to-agent-a2a/llms.txt
> - AI use cases: https://avalara.ferndocs.com/docs/ai-use-cases/llms.txt
> - API versioning: https://avalara.ferndocs.com/docs/api-versioning/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://avalara.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://avalara.ferndocs.com/_mcp/server.

# Detect a Dropped Connection

* [Previous](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode-offline/)
* [Next](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode-offline/retry-or-fallback/)

Errors related to offline geocoding can be complex when the connection has dropped. Errors are generated from different locations:

* AFC Geo SaaS Pro Soap
* The operating system
* Your software development suite

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.

Set an appropriate timeout value for your needs within your application. We cannot tell you exactly what timeout value is best for you; but in our experience, interactive web applications tend to have a shorter timeout and desktop accounting programs tend to have a longer timeout.

Now that you’ve prepared for a timeout in your application, the next step is to decide whether to retry your request or fall back to saved geocoding results.

* [Previous](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode-offline/)
* [Next](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode-offline/retry-or-fallback/)

> **Note**
>
> Part of the **Communications Geo SaaS Pro SOAP guide** integration guide. [Open the full "Detect a Dropped Connection" milestone on Avalara](https://developer.avalara.com/products/communications/integration-guides/dev-guide_geo_soap/geocode-offline/) to see every page in this section.