Skip to main content
This page previously described sync/pipeline/RBAC/API troubleshooting for features Data Hub doesn’t have. It’s been rewritten around the issues that are actually documented.

A variable shows “Offline” but the source is actually sending data

This is a known category of issue — the reception status displayed in Data Hub doesn’t always match the true state of the underlying data source. If a variable shows Offline but you have reason to believe the source is actively sending data, this may be a display bug rather than an actual data gap. Check the variable’s raw recent readings (via its Graph/Table view) before assuming the source itself is down.

A variable genuinely isn’t receiving data

1

Confirm the data reception state

Open the variable’s detail view and check whether it shows Online or Offline. Offline means no data for more than 12 hours.
2

Check the data source, not just the variable

Data gaps are often at the source level (a weather station, an Obvius logger, an API integration) rather than isolated to one variable. Check whether other variables from the same data source are also affected.
3

Check the Logs tab

The metered entity or variable’s Logs tab may have notes about known issues or recent changes relevant to the gap.
This page is a stub for a full escalation path (who to contact, what information to gather) — that hasn’t been documented yet.

A derived variable’s formula isn’t showing in its Details view

This has been a known issue for derived variables specifically — the formula and dependency list sometimes fail to populate in the variable’s Details section even though the variable is calculating correctly. If you see this, it’s a known display gap rather than something misconfigured on your end.

Export isn’t working on a visualization

Export has been an active area of bug-fixing across visualization types (heatmap, load profile, multi-variable charts). If clicking Export does nothing or produces an unexpected result, it may be a known issue with that specific chart type rather than a configuration problem.