General Troubleshooting¶
Data Loading and Connectivity Issues¶
Q: My data isn’t appearing or processing correctly — what should I check?¶
| Problem | Solution |
|---|---|
| File Loading: Data files fail to load or show unexpected results. | - Ensure your files (CSV, Parquet, JSON) meet Falkonry specifications. - CSV specifics: - Use commas ( ,) as separators.- Avoid summary lines or metadata in the file content. - Verify a consistent time identifier and format across all files. - Ensure each file has a unique name. - Confirm all files of the same type share a consistent schema. |
| Time Configuration: Data appears at the wrong times or isn’t processed. | - Time Format: Match the connection configuration (ISO 8601, Unix epoch in seconds, ms, µs, or ns). - Time Identifier: The column/key must exactly match the Time Identifier in your connection (case-sensitive). - Time Zone: Check that time zones in your data align with the system; mismatches can shift timestamps. - Time Format Documentation. |
| Data Content and Quality: Data points are missing or not plotted correctly. | - Numeric signals ignore non-numeric values — gaps will appear in charts. - Only US number format is supported ( 1.23). Values like 12,3 are dropped.- The system can handle gaps or varying sampling rates without extra data wrangling. - MQTT live streams: Expect a ~15-minute buffer before data appears. Pattern detection and rule processing are low-latency after that. - MQTT Data Format Documentation. |
| Connection Status and Signal Approval: Data isn’t flowing into the system. | - Check your connection status: - TEST: Validation and drafting only. - PRODUCTION: Continuous live processing. - PAUSED: No new data transfers. - Signals must be approved from Draft Signals before data is processed. - Connection Status and Signal Approval Documentation. |
| Synthetic Signals and Transformations: Derived or cleaned signals aren’t working. | - Verify Jinja2 logic for synthetic signals or cleaning rules. - Test transformations thoroughly in TEST before moving to production. - Template Documentation. |
Signal Management and Organization¶
Q: Signals aren’t displaying correctly or behaving unexpectedly — what do I check?¶
| Problem | Solution |
|---|---|
| Signal Data Types: Signals analyzed incorrectly. | - The system auto-detects numeric or categorical types from initial data. - Adjust types in Draft Signals if needed. For example, 1/0 state signals may need Categorical.- Approved signal types cannot be changed later. - Signal Approval |
| Signal Naming: Confusing or duplicate signal names. | - Avoid renaming approved signals — it can break references. Coordinate with Falkonry if renaming is necessary. - Use unique, human-readable names, optionally with prefixes for equipment or components. |
| Signal Metadata and Properties: Visualization or rules behave unexpectedly. | - Verify metadata: description, unit, min/max thresholds. |