Common issues you may encounter in ArcGIS Velocity when ingesting data are described below as well as recommended solutions. If you encounter an issue that's not addressed below, check the Esri Community and contact Esri Technical Support.
For issues and solutions related to accessing the Velocity app, signing in, or creating and starting items, see Troubleshoot.
General feed behavior
For other feed or data source types, the time it takes to sample data may exceed the time-out for sampling. This may be due to the data being too large or there not being enough samples received during the sampling period. Try resampling or use the workflow to manually enter samples.
Ensure that the schema defined on the feed or data source matches the incoming data and the data is externally accessible. Consider the following:
- Did the samples retrieved on the feed or data source configuration encompass all possible attributes?
- Did you provide samples that do not match the incoming data?
- Did the format of the data change since the feed or source was configured?
- Is the geometry configured correctly?
- Is the external system or resource still accessible on the internet with the defined connection properties?
Ensure that Velocity can still connect to the external system or resource (broker, website, cloud IoT resource, or other). Try editing the feed or data source and resampling data as the configuration process checks for connectivity. Creating a new feed or source may be faster than troubleshooting an existing source. If the schema changes, it may affect analytic outputs using the feed or data source and you may need to re-create them.
If the issue is with a feed that polls periodically for data, consider the frequency of the polling schedule. Polling occurs on regular clock intervals as opposed to the start time of the feed. For example, if a feed is set to poll for data every 5 minutes, and the feed is started at 8:03 a.m., the first request for data will occur at 8:05 a.m., the next at 8:10 a.m., and so on. For data that changes infrequently, a best practice is to test the feed with a polling interval of every 10 or 30 seconds to ensure that the data is successfully retrieved; then update the feed with the appropriate polling interval later.
Field types may be incorrectly defined.
- Defining a field as numeric type when string character values are also present in the data associated with that field results in no data being ingested.
- Setting a Float64 field as a Float32 field alters the data values by dropping precision.
For date fields created from strings, ensure that the data formatting string is accurate for all incoming date values.
General feed behavior
The subscription limit may have been exceeded. For ArcGIS Velocity Standard and Advanced license levels, the overall feed velocities of incoming data is limited. If an individual feed or total overall feed velocity exceeds the license level limit, feeds may stop. For details, see Licensing.