Troubleshooting
This page links common symptoms to likely causes and fixes, especially for data ingestion and data sources. For full detail on parser settings and behaviour, see Data Sources.
Data source shows OVERDUE
Symptom: The data source or parser is flagged as OVERDUE.
Cause: No data has been collected within the Out of date period configured on the data source (e.g. no new file found or no new readings in the expected time window).
What to do:
- Check that the FTP server (or upstream system) is actually uploading new files to the path the data source uses, and that the File match pattern matches those files.
- Confirm the Collection interval and Out of date period are appropriate for how often you expect new data (e.g. if files arrive hourly, the out-of-date period should be longer than one hour).
- Use the data source Logs tab to see when the last file was processed and whether any errors occurred.
- If you need to backfill or re-read old files, use Reprocessing data: adjust the “Last reading datetime” or “Last file datetime” and run a manual collection.
No or wrong data in charts/readings
Symptom: Charts or readings are empty, or values look wrong (e.g. wrong column, wrong scale).
Causes and fixes:
| Likely cause | What to check / do |
|---|---|
| File not mapped | Ensure the File to map (and File match string on the data source) matches the file that is actually on the FTP server. Check the data source Logs to see which file was processed. |
| Wrong Labels row or Data row | In file mapping, the Labels row must be the header row that names each column; the Data row must be the first row of data (so the header is not parsed as numbers). If these are wrong, columns will not align with sensor mappings. |
| Wrong datetime column or format | Select the correct Datetime column and set the Datetime format to match how datetimes appear in the file (see Parser settings for format tokens). Wrong format or timezone can cause rows to be skipped or shifted. |
| Timezone mismatch | Set the data source Timezone to the timezone in which the file’s datetimes are written. The project timezone only affects display. |
| Sensor mapping missing or wrong | Under the data source, Sensor mapping must link file columns (or row fields) to the correct sensor inputs. If a sensor was added after the file was first processed, reprocess after mapping. |
Last reading / last file datetime and reprocessing
Symptom: You changed the parser (e.g. Labels/Data row, datetime format, or sensor mappings) and expect to see different data, but nothing changed.
Cause: The platform only processes new data after the stored Last reading datetime and Last file datetime to avoid reprocessing the same file repeatedly.
What to do: Use Reprocessing data: reset or set “Last reading datetime” and “Last file datetime” to the point from which you want to re-read files, then use Run to trigger a manual collection. After that, new mappings or parser settings will apply to the reprocessed data.
Logs and errors
Use the data source Logs tab to see:
- When files were collected and how many readings were processed.
- Any parser or connection errors.
If logs show repeated errors (e.g. “file not found”, “parse error”), fix the cause (path, file match, delimiter, datetime format, or column/row selection) then reprocess if needed.
API and token issues
- 401 Unauthorized: Check that you are sending the token in the
Authorization: Bearer {token}header and that the token is the one from your profile. If the token was rotated or revoked, use the current value from the UI. - 404 or wrong resource: Confirm you are using the path and IDs from the correct endpoint (e.g.
proj_idfor Readings vsproject_idfor the Projects endpoint). See API Paths. - 429 Too Many Requests: You have exceeded the rate limits. Use the response headers to see usage and back off or batch requests.
For more on authentication and paths, see Authentication and API Paths.