Troubleshooting HERO Reports

A table has blank columns

New results should never display or export a declared column without backing data. Capture:

• the approximate time;
• the HERO thread/message;
• the report request;
• whether the table, CSV, or XLSX was affected; and
• any visible failure copy.

Do not manually relabel the export as correct. Check Hero Health for an Output contract cluster. Legacy stored visualizations may fail closed rather than render their old invalid shape.

HERO says the result could not be delivered

This means the database result and requested table structure could not be reconciled safely. Rephrase the request with explicit fields, or ask for a narrower report. The failure is recorded for internal review.

Only 1,000 rows are available

HERO intentionally caps loaded table data at 1,000 rows. The table shows 50 rows per page. CSV and Build Excel include all loaded validated rows, not only the current page. If the total exceeds 1,000, narrow the date, property scope, status, or record type.

Hero Health is missing

Hero Health is database-administered. Confirm that the signed user’s user_profiles.id exists in hero_health_admins.user_id. There is no settings screen for this.

Digest or spike email did not arrive

Check:

• the admin row still exists;
• user_profiles.email_address is present;
• the delivery ledger’s recipient status;
• Resend configuration; and
• the task schedule.

Weekly digests skip when there are no new clusters, guard fires, or repairs. Spike alerts send once per episode and re-arm only after returning to baseline.

Never include access tokens, provider keys, raw repair fragments, or resident personal information in support messages.