Workspace

Checkout Service

This is a live, pre-populated demo — no account, no timer, and it never changes: a monitor incident, a crash regression, and a resource alert, each with its own AI analysis, one scored release, and the public status page customers would see. Everything on this page is read-only demo data.

Defects — three sources, one list

A monitor incident, a crash spike, and a resource-saturation event all land here the same way, each with the AI analysis already attached.

Title	Status	Severity	Priority	Source	Created
api-gateway: elevated 5xx after deploy	resolved	high	high	Monitor	2026-09-18
NullPointerException in CheckoutViewModel.submit() — spiking after v2.4.1	triaged	critical	urgent	Crash	2026-09-18
orders-worker CPU saturation — 94% sustained for 12 minutes	new	high	high	Resource alert	2026-09-18

Resolved incident, diagnosed

Monitor incident

api-gateway · production

highRESOLVED

Started: 2026-09-18 09:14:00
Resolved: 2026-09-18 09:41:00
Downtime: 27m

AI diagnosis

84%

Latency and 5xx rate spiked together right after the 09:12 deploy — consistent with DB connection-pool exhaustion. The deploy dropped the configured pool size from 40 to 20 connections; /orders writes started queueing under normal peak load and the queue drained once the pool was resized back to 40 at 09:38.

Opened defect def_demo_monitor — see below.

Crash signature — grouped, attributed, flagged

Crash signature

CheckoutViewModel.submit() — NullPointerException

a1b2c3d4-checkout-submit-npe

fatalOPENREGRESSION · v2.4.1

Occurrences jumped 2250% after release 2.4.1 shipped(2 before → 47 after)

Source

sentry

Platform

web

Project

Checkout Service

Occurrences

Affected users

213

First seen

2026-09-18 11:05:00

Last seen

2026-09-18 13:58:00

Opened defect

def_demo_crash

This is a demo — start free to do this for real →

AI analysis

gpt-5-mini · prompt v1.0.0 · 2026-09-18 11:06:10

null_pointer

81%

Suspected root cause

CheckoutViewModel.submit() reads the cached cart total before the async pricing-refresh call introduced in 2.4.1 resolves, so a fast double-submit or a slow network hits the field while it is still null.

Suggested fix

Await the pricing-refresh promise (or fall back to the last known total) before reading cart.total in submit().

Affected versions

2.4.141
2.4.06

Affected devices

Chrome 128 / macOS19
Chrome 128 / Windows15
Safari 17 / iOS13

Grouped occurrences (3 stack traces folded into this one signature)

Expand stack traces

2026-09-18 13:58:002.4.1 · macOS 15.1 · Chrome 128

TypeError: Cannot read properties of null (reading 'total')
    at CheckoutViewModel.submit (checkout-view-model.ts:88:34)
    at async onSubmitClick (checkout-form.tsx:52:5)
    at async HTMLFormElement.handler (checkout-form.tsx:19:3)

2026-09-18 12:41:002.4.1 · Windows 11 · Chrome 128

TypeError: Cannot read properties of null (reading 'total')
    at CheckoutViewModel.submit (checkout-view-model.ts:88:34)
    at async retrySubmit (checkout-view-model.ts:104:11)
    at async onSubmitClick (checkout-form.tsx:52:5)

2026-09-18 11:12:002.4.1 · iOS 18.0 · Safari 17

TypeError: null is not an object (evaluating 'cart.total')
    at CheckoutViewModel.submit (checkout-view-model.ts:88:34)
    at async onSubmitClick (checkout-form.tsx:52:5)

The defect it opened

Defect · opened automatically

NullPointerException in CheckoutViewModel.submit() — spiking after v2.4.1

def_demo_crash

triagedcritical

project checkout · created 2026-09-18 · opened from crash signature crs_8f2a1c

Auto-filed from crash signature crs_8f2a1c. 47 occurrences across 213 users since v2.4.1 shipped, concentrated in the new async pricing-refresh path on CheckoutViewModel.submit(). No manual triage has happened yet — this is exactly what an auto-filed regression defect looks like on arrival.

This is a demo — start free to do this for real →

Analysis (AI)

gpt-5-mini · prompt v1.0.0 · 2026-09-18 11:06:10

High confidence

This signature accounts for 47 occurrences across 213 users, concentrated almost entirely in build 2.4.1 (41 of 47) — the shape of a regression, not background noise. First seen 11 minutes after 2.4.1 finished rolling out.

Likely cause

CheckoutViewModel.submit() dereferences the cached cart total before the new async pricing-refresh call resolves, which 2.4.1 introduced. Null read on a race, not a data problem.

crash-signature:crs_8f2a1crelease:2.4.1affected-versions

Release quality score

Release

web · v2.4.1

Released

This is a demo — start free to do this for real →

Quality Score

Weighted average of dimension scores: Mobile 30%, Crash 30%, Monitor 25%, Stress 15% (raw weights; redistributed across whichever dimensions have data). Defects joins in a later phase.

Proceed with caution

Monitor82 · 31%
Crash61 · 31%
Defects68 · 38%
StressNo qualifying runs

v1 · 2026-09-18T14:05:00.000Z

Monitor dimension

82 / 100

Incidents during the release window, by severity.

1 incident (high severity) — the api-gateway connection-pool exhaustion above, resolved in 27m.

Crash dimension

61 / 100

Production crashes during the release window, weighted by severity and category.

1 signature, 47 occurrences, 1 fatal — the CheckoutViewModel regression above, flagged this release.

Status page

Public status page · no login

CleverQA Checkout

Degraded performance

checkout-api
CPU saturation under investigation
api-gateway
Resolved incident 2h ago
orders-worker
No issues reported
auth-service
No issues reported

This is what CleverQA looks like on day one.

Every card above is demo data — connect your first service and CleverQA builds this same workspace from what's actually happening.

Start free — 14 days