Lanjutan20 menit
Buffering, Retry, and Data Quality
How the local SQLite buffer and retry queue keep data intact through outages and bad readings.
Buffering, Retry, and Data Quality
Plants lose internet. OpexFlow assumes that and keeps data anyway.
Offline-Ready
- Local SQLite buffer — holds up to 7 days of readings on the edge.
- Retry queue — failed publishes re-queue automatically.
- Auto-sync — when cloud returns, the queue drains in order.
Handling Bad Data
- Tag invalid ranges in config (e.g., negative pressure, unreachable temps).
- Publish with a quality flag so OpexMX can suppress, not panic.
- Drop sensor-disconnect events into a separate review queue.
- Set alerts for sustained bad-quality streaks, not single blips.
Resync After Outage
- Verify buffer drained by comparing edge and cloud counts.
- Investigate any gaps longer than the buffer window.
Tips
Treat data quality as a maintenance task. Assign an owner who reviews the bad-data queue weekly.