Inspection workorder page crash — bad data shape causes full page exception

Objective

• Identify the data shape or missing field that causes the inspection workorder page to throw a client-side exception on render.
• Harden the inspection workorder UI so records with unexpected or malformed data do not produce a full page crash.

Background

Every visit to inspection 1008599797 since June 12, 2026 has resulted in a $exception in PostHog — no successful pageviews across 5 distinct users. This is the primary contributing factor to the reported incident (SWF – 101 Edward Ave) where staff were unable to cancel the inspection or add notes: the UI was never usable.

The crash is data-specific — something about the shape of this record causes a component in the workorder shell to fail during render. Inspection 1008599797 is the first known example of this pattern and should be used as the repro case, but the fix should address the underlying render fragility rather than patching this specific record. The exact component and field is unknown until the PostHog stack trace is pulled.

This is the first reported instance of this failure pattern. Treating as an edge case until a second occurrence or broader data pattern is identified.

• Affected inspection: 1008599797
• Front text thread: TC cancellation request
• Related issue: ATT-1963 (Attik job cancel not confirmed to Spectora when _spectoraJobId is absent)

Repro Steps

1. Log in as a user with access to the SWF company and open inspection 1008599797.
2. Expected: Workorder page loads (workorder / activity-feed / integrations tabs).
3. Actual (PostHog): Page throws a client $exception on every visit since Jun 12, 2026 (multiple users, Chrome/Edge, various tabs).
4. Pull the PostHog exception stack trace for this inspection URL to identify the failing component and field.

Product Decisions

Locked

1. Bug. Staff could not perform cancellation or add notes because the page was entirely broken.
2. The fix should harden the render path broadly — not patch the specific record — so other records with unexpected data shapes do not produce a full page crash.
3. First reported instance — tracking as edge case. Priority to be revisited if additional records are identified.

Open

1. Which field or component triggers the exception? Requires PostHog stack trace or local repro with the production record's data shape.
2. Is the crash limited to this one record or are other records with a similar data shape affected?

Scope

Frontend

• attik-frontend/src/app/tools/inspections/[id]/page.tsx — server fetch and shell render; passes data to InspectionWorkorderShell, WorkorderPage, InspectionActivityFeed
• Investigate null/undefined guard gaps in the above and any child components surfaced by the PostHog exception trace (exact component TBD)

Out of scope

• Fixing or patching inspection 1008599797 directly
• Notes or cancellation API behavior (unblocked once the page loads)
• Spectora cancel confirmation gap (tracked in ATT-1963)

References

• Inspection 1008599797
• Front text thread — TC cancellation request
• Slack intake (PostHog summary): attachment on this ticket
• ATT-1963 — Spectora cancel confirmation gap (related)