Both are in Settings in the TravelTime tab. Robust Mode stops one bad location from failing a whole run. The Hits Per Minute limit stops a run from going over your plan’s rate limit.
Robust Mode
Robust Mode is on by default.
On: if the API rejects a search, for example because a location is in the sea, the tool skips that search, notes it in the tool messages and carries on. It writes all the successful results and ends with a warning listing the searches that failed.
Off: the first failed search stops the whole run.
Some tools always stop on a failed search, whatever the setting, because a missing location would make the result wrong rather than just smaller:
Isochrone tools with Result Aggregation set to INTERSECTION
All Location Analytics tools: Territory Map, Reachability Heatmap, Doughnut Areas, Cannibalisation and Location Allocation
Hits Per Minute limit
The limit is off by default. Turn it on and enter your plan’s hits-per-minute limit to avoid 429 (too many requests) errors. When a tool is about to go over the limit, it pauses for 60 seconds and then carries on.
What counts as one hit:
one isochrone
one H3 search
one route
one Travel Time Matrix search: one per departure location, or one per arrival location for arrival searches
Geocoding and Data API requests don’t count towards the limit.
The count starts again with each tool run, so running several tools back to back can still go over your limit. Leave a minute between big runs, or check your usage in your TravelTime account.