> 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.

# Retry or Fallback

* [Previous](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode-offline/detect-dropped-connection/)

After your application detects a timeout or an error, it must next make a decision whether to retry the request or fall back to saved geocoding results.

### Retry a Request

Retry your request a few times if timeouts are still being returned:

1. Retry the request
2. Wait 1 second and retry the request
3. Wait several seconds and retry the request

It’s important that you don’t retry so often that your attempts are mistaken as a denial-of-service attack. Limit your retries to 5 to 10 attempts to prevent a backlog of concurrent requests and allow system time to recover.

Some applications attempt to reuse HTTP connections. In the event that you experience a connection disruption, we suggest creating a completely new connection for the next attempt.

### Fall back to saved geocoding results

Save geocoding results quarterly by running processing addresses or latitude/longitude coordinate pairs that cover your business needs (such as all new customer data received within the last 3 months). In the event of a timeout or other type of error, fall back to these saved results.

Things to consider when falling back to saved geocoding results:

* AFC Geo SaaS Pro Soap is updated on an off-quarter cycle. Map data and [special tax jurisdictions](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/special-tax-jurisdictions/) are generally only updated during this quarterly release

* PCode and other characteristics of a location do not change often, if at all, once the data has been set

* [Special tax jurisdictions](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/special-tax-jurisdictions/) may be added or removed from a primary jurisdiction during a quarterly release based on the local jurisdiction legislation

* [Previous](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode-offline/detect-dropped-connection/)

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