Docs/Data connections
Runs and troubleshooting
Trace accepted submissions, diagnose missing readings, and verify calculations and notifications.
Runs record processing operations such as ingestion and recalculation. They help distinguish successful submission from completed processing and make failures easier to investigate.
Inspect a run
Open Ingestion → Runs or follow a run link from an API connection, pipeline, instrument, or recalculation banner. Review the operation type, state, timestamps, error summary, and any progress information.
Depending on your access and the operation, a run can show the submitted data point, resolved output, validation details, or recalculation progress. Some diagnostics require a management capability and are not available to every project viewer.
Follow a missing reading
Work through the data path with a specific instrument and source timestamp:
- Source: confirm the file, upstream system, or sender produced the expected reading.
- Access: check connection health, grant availability, lifecycle, and pipeline enablement.
- Submission: locate the relevant file attempt, delivery, or Ingest API run ID.
- Processing: inspect failed or rejected work and its reported reason.
- Destination: verify the instrument name, site, variable name, value type, and timestamp.
- Display: check the selected time range, hidden variables, archived history, and your access scope.
This avoids repeatedly resending a point that is already stored under a different timestamp or instrument name.
Common symptoms
| Symptom | What to inspect |
|---|---|
| API returns success but no value appears | Follow returned run IDs; acceptance is not processing completion. |
| FTP pipeline is enabled but idle | Connection and grant state, remote target, last check, health, and file attempts. |
| Some CSV rows fail | Parser diagnostics, missing markers, type conversion, timestamp format, and ordering. |
| Graph is empty but readings exist | Time range, decimal variable selection, hidden settings, and archived history. |
| Calculated values look unchanged | Recalculation status; previous current values remain visible during rebuilding or after failure. |
| Affinity backlog grows | Separate capture and processing states, capacity incidents, quarantine, and recovery messages. |
| Missing-signal condition did not run | Whether a new non-skipped project point arrived to trigger evaluation. |
| Anomaly appears without an email | Captured action, resource availability, cooldown, action execution state, and recipient details. |
Retry with context
Resolve the reported cause before retrying. FTP reprocessing reads one current file revision without moving the normal cursor. Affinity recovery retries retained work under its recovery flow. Ingest API retries should use the documented idempotency behavior.
When asking an administrator for help, include project and instrument identifiers, the affected timestamp range, run or attempt IDs, and the visible error summary. Keep API keys and upstream credentials out of screenshots and support messages.