Skip to main content
Use this page to troubleshoot quality checks and completeness gaps.

​
Frequently asked questions

Issues are record-level problems (for example, connection errors or bill anomalies). Completeness gaps indicate missing expected coverage over time.
Not always. It can reflect delayed utility publication, connection downtime, or start-date settings. Validate connection status and expected billing cadence first.
Start with active connection failures, then unresolved bill anomalies, then completeness gaps that affect your reporting period.
Yes, but flagged bills are often excluded by default in exports. Review filter settings and issue severity before final reporting.
Retry and narrow filters (company/site/date). If errors persist, capture the URL and error message for support so the failing scope can be diagnosed quickly.
For gaps with site context, Inspect opens the Aggregation Inspector for that month. It breaks down how site totals are built from meters, which helps explain unexpected completeness or usage totals. See Completeness for the full sheet layout.
Drilling from a site row into an account can open a second panel on top so you do not lose site context. Close the top panel to return to the main swim lane.
Yes. Filters are stored in the URL—copy the address bar after setting period, severity, sites, and any + Add Filter options to share the same view with a teammate.
The cell reflects whether expected usage data (or bills, depending on configuration) exists for that entity and month. Flagged bills, wrong site assignment, or calendar boundaries can still show a gap. Use the gap detail Bills and Usage tabs to see what Nectar counted for the period.

Data quality overview

Summary of quality workflows and detection types.

Issues

Diagnose and resolve flagged problems.

Completeness

Track period-level data coverage and gaps.

Data input FAQ

Troubleshoot upstream collection failures.