Troubleshooting Errors

Guide to troubleshooting some of the possible errors when running the TravelTime add-in for ArcGIS Pro

Data Issues

Unreachable areas

All lat-long coordinates being used for any of the tools must be in a physically reachable area. 

Locations on water (e.g a river) or in very remote locations will return an error:

Unreachable areas_2

This will sometimes happen when the input layer has been created by converting polygon areas into points, e.g when using the centroid of zip codes / postcodes

International borders

The tools do not currently support cross-border travel. All points must therefore be in the same country, else an error will be returned:

Unreachable areas

This error will also be thrown when attempting to run a tool in a country that we do not currently support. For a full list of supported countries, please see here

Blank or corrupted data

Blank rows in an input file, or data that is corrupted (e.g with null geometry) will return an error:

Blank data

An input file may contain blank rows if it has been generated using a Geocoder and not all the addresses were successfully geocoded

Tool Configuration

Arrival/departure date

We typically support public transport data for two weeks back from today's date, and six weeks forwards.

For example, on 1st June 2020, we would typically support any searches within a window from 18th May 2020 - 13th July 2020.

Running a tool with an arrival/departure date outside of this window will return an error:



The Output layer for any of the Simple or Advanced tools must be saved into the project Geodatabase:


File naming 

Files saved into the Geodatabase have to follow the Esri naming convention:

1. No spaces or special characters (except for underscores _)

2. Name cannot start with a number of an underscore

If the file name you are trying to save an Output layer as does not follow these rules, an error will be returned:

naming convention

Environment configuration

When running any of the Simple or Advanced tools, only the Parameters tab in the Geoprocessing pane should be configured:


Changing values in the Environments tab can cause errors, for example, if the Output Coordinate System is changed:

Environment changes

Non-unique IDs

When running any of the Advanced Tools, where the ID fields are configurable, the field selected as the ID must be unique amongst all points. If this ID is not unique, an error will be returned:

unique ids


Network issues

SSL blocked

By default the add-in runs with SSL enabled. This can occasionally cause issues when operating through a proxy or firewall, as Pro may not be able to connect to the API.

If you believe this may be the issue, please contact your internal IT teams for guidance.


For support on overcoming errors or to flag an issue/bug, please contact