Help Center / Troubleshooting & FAQ

Troubleshooting & FAQ

Answers to the most common questions and the issues users hit. If something here doesn't resolve it, the relevant topic page is linked alongside.

Jump to

"Failed to load content packs"

This appears when you opened the app as a file:// path. Browsers block the fetch() calls that load the jurisdiction / playbook / scenario / letter data from disk. Fix: serve the app over HTTP. Any static server works; for example, from the project folder run python3 -m http.server 8000 and open http://localhost:8000/app/index.html. See Opening the app.

A deadline looks wrong

Work through these in order:

  1. Check the clock anchor. Most deadlines run from Discovered at. If that's set to "now" by default, correct it to the real discovery time and recompute.
  2. Check the basis. Some clocks are business days, not calendar days — see below.
  3. Check the rule type. The SEC clock runs from materiality, not discovery; CA/OK AG clocks run from the notice date — see below.
  4. Check proposed vs in-force. A proposed item (amber PROPOSED pill) is for planning, not filing — see below.
  5. Confirm with the citation. Each row shows its statute / citation; verify against it, and ultimately with counsel.

Business-day vs calendar: my deadline is off by a day or two

That's usually the holiday-aware business-day math working correctly. Clocks marked as a business-day basis (e.g. the SEC's 4 business days) skip weekends and observed U.S. federal holidays, so the calendar date lands later than a naive "trigger + N days." Calendar-basis clocks (most state notices, HIPAA 60 days, the 72-hour framework clocks) count every day including weekends and holidays. See Business-day math + federal holidays for the full holiday list and which clocks use which basis.

My AG clock is anchored to a fallback instead of the actual notice date

This affects the two post-individual AG clocks — California (SB 446, +15 days) and Oklahoma (SB 626, +60 days) — whose AG deadline runs from when you notified that state's residents, not from discovery. Until you record the real notice date, Klaxon anchors to the individual-notice deadline (the latest lawful start), which is the conservative latest AG due date, and the row shows an amber fallback — record notice date pill.

Fix: in the incident facts, enter the real per-state notice date (e.g. CA:2026-06-10) in the "Individual-notice date sent, per state" field and recompute. The AG deadline re-anchors to that date + the statutory days and the pill turns green (from actual notice date). See post-individual AG clocks.

What does the PROPOSED pill mean? Should I file on it?

An amber PROPOSED pill marks a rule that is not yet enforceable — currently the HIPAA 72-hour incident-report item (NPRM, no final rule) and CIRCIA's 72h/24h reports (CISA final rule pending). They're shown so you can plan, but do not file on them and they do not replace the in-force deadlines (e.g. the proposed HIPAA item does not change the authoritative 60-day HIPAA deadlines). Items without the pill — SEC Item 1.05, CA SB 446, OK SB 626, all state and other framework rules — are treated as in force. See Proposed vs final labeling.

An obligation I expected is missing

An obligation I didn't expect appeared

The engine adds a state's individual notice whenever you have any affected residents there, and adds the AG notice when the count meets the threshold. If you see an unexpected row, re-check your per-state counts and flags — a stray entry like NY:1 will add NY (which notifies its AG at 1+). The citation on the row explains why it triggered.

I see a "TIMELINE TAMPERED" badge

The timeline's SHA-256 hash chain no longer verifies — a stored event was altered or removed outside the append-only flow (e.g. edited directly in browser storage, or partial corruption). The badge tooltip shows the first broken event index. Preserve the state, compare against any earlier auditor-bundle export, and treat the pre-break export as authoritative. Full guidance: Timeline integrity → If you see "TIMELINE TAMPERED".

There's no integrity badge at all

The badge appears once the timeline has been sealed, which happens when the incident renders with at least one event. A brand-new incident before its first render may briefly show no badge. Open the incident; it should show timeline verified.

Scheduled push is unavailable / I'm offline

That's expected. Scheduled push is the only network-dependent feature and is opt-in. If you're offline, not signed in, or the optional cloud module didn't load, the push controls won't work (status: "delivery/scheduling unavailable") — but the local reminder cascade preview keeps showing everything that's due with no network. The deadline math never depends on the cloud. See Scheduled push → When push is unavailable.

My incidents disappeared

Incidents live in your browser's localStorage for the profile and browser you used. They'll be missing if you switched browsers/profiles, used a different machine, or cleared site data. There's no server copy by design. Going forward, export the auditor bundle / PIR regularly to keep durable copies. See Backups.

My letter shows [[FIELD]] or "Missing required"

Unfilled merge tokens stay visible as [[FIELD]], and required-but-blank fields are listed in a red banner. Fill them in the Fields panel (required ones are marked with a red asterisk) and the preview updates live. See the missing-required-field guard.

Can I export DOCX?

Not currently. Klaxon exports letters as .txt and print-to-PDF, plus a submission worksheet. Filing-quality DOCX and direct portal submission (DIBNet / HHS have no API by design) are not part of the current build. Use the .txt in your own letterhead/mail-merge, or print to PDF. See Exporting.

The AI copilot does nothing

By design, the AI copilot is dormant until you (1) flip the hard "AI on" switch and (2) add a provider key, both on the AI Copilot tab. A key alone is not enough — while off, no key is read and no call is made. The AI only writes prose; it never sets legal deadlines. See the AI section.

Is there a multi-user / cloud war-room?

The current build is local-first and single-machine. There is an opt-in cloud seam for sign-in, evidence publishing, and scheduled reminder push, but real-time multi-user concurrent editing and presence are not part of this build. Collaborate by sharing exports.

Which jurisdictions and frameworks are covered?

All 50 U.S. states plus the District of Columbia and Puerto Rico (52 U.S. jurisdictions), and seven frameworks: HIPAA, DFARS, GDPR, PIPEDA, Québec Law 25, SEC Form 8-K Item 1.05, and CIRCIA (proposed). See the full breakdown on Obligation clocks → Coverage.

The SEC 8-K clock seems to start from the wrong date

The SEC Item 1.05 clock is 4 business days from the materiality determination, not from discovery. Klaxon uses the incident's anchor time for this; set that time to your materiality-determination moment so the SEC clock counts correctly. Note it is also business-day math, so weekends and federal holidays are skipped. See The clock anchor and Business-day math.

Still stuck? Re-read the relevant topic page from the Help Center index — every feature is documented there with numbered steps. Klaxon is self-service by design.

← Security & privacy  ·  Back to the Help Center →