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 your request a few times if timeouts are still being returned:
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.
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: