Frontend web release incidents

Frontend web: 6 published incident types backed by 13 public reports.

The root-cause stage named most often in this group is code, in 5 of 6 incident types.

6 incident types published · 2 withheld · 13 public reports

Incident types in this group

Frontend web


Analytics event schema broken	Likelihood: low (2 public reports in 5 years)	Impact: high (2 of 2 reports: data)	2
Asset cache serves old bundle	Likelihood: medium (3 public reports in 5 years)	Impact: medium (2 of 3 reports: availability)	3
Critical path broken in one browser	Likelihood: low (2 public reports in 5 years)	Impact: medium (2 of 2 reports: availability)	2
CSP blocks required script	Likelihood: low (2 public reports in 5 years)	Impact: medium (2 of 2 reports: availability)	2
Form submission silently fails	Likelihood: not published (1 public report in 5 years)	Impact: high (2 of 2 reports: data)	2
Localisation strings missing	Likelihood: low (2 public reports in 5 years)	Impact: low (2 of 2 reports: degraded)	2

Withheld in this group: Accessibility regression on key flow, Hydration mismatch blank page. Reasons per route

Risk grid

Risk grid: count of incident types per likelihood and impact cell, from data/risk.json
Likelihood \ Impact	Impact: high	Impact: medium	Impact: low
Likelihood: high	0	0	0
Likelihood: medium	0	1	0
Likelihood: low	1	2	1
Impact unrated or likelihood not graded	1

Table equivalent: incidents per cell

Incident	Likelihood	Impact
Analytics event schema broken	low	high
Asset cache serves old bundle	medium	medium
Critical path broken in one browser	low	medium
CSP blocks required script	low	medium
Form submission silently fails	not-published	high
Localisation strings missing	low	low

Root-cause stages

Stage	Incident types naming it
code	5
release-process	4
third-party	2
config	1

Fewer than 2 reports in this group state both the change time and the detection time; no median is printed.

Only on this page

Asset cache serves old bundle is the incident type in this group whose root causes do not include the code stage; its causes are introduced at config and release-process.

Group checklist

The first pre-release item of each published incident type in the group.

GR-01Analytics event schema broken: Run the capture script integration suite against every snippet version still installed on client sites, not only the upcoming one. integration
GR-02Asset cache serves old bundle: Scan the build output and fail the release when any JavaScript file URL lacks a content hash in its file name. config
GR-03Critical path broken in one browser: Load the web interface on an iOS 16.2 simulator, or the oldest iOS version in the support policy, and confirm it renders past the background picture. compatibility
GR-04CSP blocks required script: Reload the single-page app at least 50 times in a real browser against the release candidate and confirm every load renders the app shell with no CSP violation in the console. e2e
GR-05Form submission silently fails: On a deploy preview, submit the contact form and the estimate form and confirm each submission appears in the form capture store, not only that the thank-you page loads. e2e
GR-06Localisation strings missing: At the release gate, compare the string keys of each shipped locale with en-US and fail on any new key with no translation. config

Questions

What causes Frontend web incidents?

Published incident types in this group name these root-cause stages: code (5), release-process (4), third-party (2), config (1).

Which pipeline stage introduces most Frontend web incidents?

The code stage, named in 5 of 6 published incident types in the group.

Which test classes catch Frontend web incidents?

Test classes listed on the group's incident pages: synthetic monitoring (6), end-to-end tests (5), configuration and environment tests (2), integration tests (1), contract tests (1), compatibility tests (1), security tests (1).

How quickly are Frontend web incidents detected in public reports?

Fewer than 2 reports in this group state both the change time and the detection time, so no median is published.

How likely are Frontend web incidents compared with each other?

Analytics event schema broken: low likelihood, high impact; Asset cache serves old bundle: medium likelihood, medium impact; Critical path broken in one browser: low likelihood, medium impact; CSP blocks required script: low likelihood, medium impact; Form submission silently fails: not-published likelihood, high impact; Localisation strings missing: low likelihood, low impact.

What should a release checklist for Frontend web include?

The group checklist collects the first pre-release item of each of the 6 published incident types; each item names the test class that checks it.