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.

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.