Demo
Sign in

marks webhook as delivered after callback

tests/e2e/webhooks/delivery.spec.ts

failed
3m 38s
chromium
Diagnosis

See the failing step first, then validate the likely cause with the trace and artifacts.

Failure summary
TimeoutError
High confidence
Webhook status stayed “Processing” until the callback completed after the assertion timeout.
This is a strong showcase of Sentinel's timing analysis: the UI symptom is secondary, and the interesting signal is the delayed backend completion.
Parsed failure signal
TimeoutError: Webhook status stayed “Processing” until the callback completed after the assertion timeout.
Evidence
  • The failing step waits on a response-dependent UI update.
  • The run behaves like a race: sometimes the callback lands in time, sometimes it does not.
  • The most valuable debugging path is comparing the slow run against a passing run.
What to check next
  • Inspect the response timing around the webhook callback.
  • Wait on the backend signal before asserting the final UI state.
  • Compare callback timing against the last known good run.
Suggested fix
Gate the assertion on the callback completing instead of only waiting on the UI text.
await page.waitForResponse((response) =>
  response.url().includes('/api/webhooks/delivery') && response.ok()
);
await expect(page.getByTestId('webhook-status')).toHaveText('Delivered');
Loading failing step…
Evidence

Open the same artifacts a developer would inspect in a real failing run.

Evidence workspace

Best first click for step timing and action flow.

Scripted demo
Trace timeline
08:07:18 Trigger webhook send
08:07:19 Poll UI for delivery status
08:07:24 UI still shows “Processing”
08:07:25 Assertion timeout fires
08:07:27 Callback finally returns 200
Start with trace
Trace is the best first click because it shows whether the callback finished before the assertion ran.
Screenshot and logs
The screenshot usually only shows the symptom, not the true timing cause.
Logs help confirm whether the callback was slow, retried, or never completed.
Advanced analysis

This is where the product proves it is more than an artifact viewer.

Failure intelligence

Computing failure intelligence…