Tag
#errors
28 playbooks tagged #errors.
- ops 1 hour to set up · advanced
Nightly Routine: draft PRs for low-risk silent bugs
Routine runs at 2am, picks the top silent bug, investigates it, opens a draft PR if the fix is small and contained. Lights-out triage for the next morning's review.
#routine#automation#auto-fix#ops - debugging 30 seconds · beginner
Diagnose a customer complaint in 30 seconds
Paste a customer message. The agent pulls their session, finds the error they hit, walks their funnel, and tells you what to reply.
#analytics#customer-support#replay#distinct-id - debugging 2 minutes · intermediate
Track crash-free user rate per app version
Distinct users who hit a crash divided by DAU, per app version. The industry-standard mobile health metric — surface version-by-version drops fast.
#mobile-app#crash-free-rate#app-version#sentry-alternative - debugging 30 seconds · beginner
Find what broke after your last deploy
Diff error fingerprints before and after the latest deploy SHA. Surface regressions in 30 seconds, including a candidate fix.
#deploys#post-deploy#oncall#regression - debugging 2 minutes · intermediate
Rank errors by revenue impact, not raw count
Multiply users-affected by their plan ARR to surface the bugs costing real money. Stop triaging by event volume.
#revenue#triage#account-health#b2b - debugging 5 minutes · intermediate
Find integration setup failures
Show where customers fail while connecting integrations so engineering and CS can fix the highest-impact setup blockers.
#analytics#integrations#onboarding#customer-success - debugging 5 minutes · intermediate
Find queue latency and dead-letter spikes
See which background jobs are backing up, retrying, or landing in dead-letter queues before customers notice stale state.
#analytics#background-jobs#queues#infra - ops 3 minutes · intermediate
Release health scorecard after every deploy
Summarize a deploy with new errors, affected users, key metric deltas, and the next engineering action in one chat response.
#analytics#deploys#releases#oncall - ops 5 minutes · intermediate
Audit sourcemap coverage for minified errors
Find which production errors cannot be unmangled because sourcemaps are missing, stale, or uploaded under the wrong release.
#sourcemaps#releases#frontend#ops - ops 2 minutes · beginner
Review stale or dangerous error suppressions
Find suppressions that are hiding high-volume, high-impact, or recently regressed errors before noise rules mask real incidents.
#suppressions#oncall#governance#ops - ops 5 minutes · intermediate
Rank support load by account
Combine errors, complaints, affected users, and plan data to show which accounts are consuming the most support attention.
#analytics#customer-support#account-health#b2b - debugging 2 minutes · intermediate
Mobile background-sync failure monitoring
Background sync, refresh, prefetch jobs fail silently and degrade UX. Group failures by task_name and network_type to find the patterns.
#mobile-app#background-jobs#oncall#infra - debugging 2 minutes · intermediate
Find IE/Safari/old-Chrome-only crashes
Split client-side errors by browser and version. Surface fingerprints concentrated in one engine — usually older Safari or a stale Chromium.
#browser#client-side#frontend#sentry-alternative - debugging 2 minutes · intermediate
Track static-asset 404s per release
Group asset 404s by URL and deploy SHA. Catch stale CDN caches and missing hashed bundles before users see a blank page.
#cdn#release#deploys#frontend - debugging 1 minute · intermediate
Diagnose CORS errors after a deploy
Find CORS-blocked requests grouped by origin and endpoint. Surface the misconfigured Access-Control-Allow-Origin from a recent service move.
#cors#deploys#post-deploy#infra - debugging 2 minutes · advanced
Find connection-pool / timeout patterns in errors
Surface DB connection exhaustion, statement timeouts, and deadlock retries. Find the original slow query starving everything else.
#database#infra#scaling#oncall - debugging 30 seconds · beginner
Find what broke after the last npm update
Tie new error fingerprints to the deploy that bumped dependencies. Spot the silent regression nobody intended to ship.
#regression#dependencies#deploys#post-deploy - debugging 3 minutes · advanced
Which user action triggers which error?
Join errors and analytics events by distinct_id and timestamp. For each top fingerprint, surface the user action that immediately preceded it.
#analytics#cross-signal#sentry-alternative#posthog-alternative - debugging 1 minute · beginner
Compare error rates between staging and prod
Diff fingerprints between staging and production. Find what's already breaking in staging that the next deploy will carry into prod.
#environments#pre-deploy#staging#oncall - debugging 1 minute · intermediate
Diagnose a flaky CI test from its error payloads
Group test failures across CI runs by error pattern. Get a verdict — real bug or timing — without the manual archaeology.
#ci#testing#oncall#flaky-tests - debugging 1 minute · intermediate
Catch display-vs-actual-stock mismatches
Find inventory sync errors trending up by warehouse and SKU before customers do. The 'in stock' display lie is one of the highest-cost bugs in ecommerce.
#inventory#ecommerce#infra#oncall - debugging 1 minute · intermediate
Detect a 429-spike before customers tweet about it
Trend HTTP 429 responses week-over-week and flag spikes. Catch third-party rate-limit tightening or a runaway customer integration.
#rate-limiting#early-warning#oncall#datadog-alternative - debugging 2 minutes · intermediate
Diagnose a bug from the session replay, not the stack
Customer reported a checkout error. Pull their session replay, read what they did in the 60s before the error. Some bugs only make sense when you see the user's screen.
#replay#customer-support#debugging#posthog-alternative - debugging 10 seconds · beginner
Find the bugs 5 people hit but no one reported
Surface real errors that affect multiple users but never get filed as tickets. The biggest source of silent churn.
#oncall#retention#saas#sentry-alternative - ops 5 minutes · intermediate
Watch staging — page only on genuinely new errors
Set up a scheduled Routine that diffs error fingerprints each hour and only pages oncall when a genuinely new failure mode appears.
#oncall#post-deploy#webhooks#automation - debugging 2 minutes · intermediate
Diagnose Stripe `card_declined` patterns
Group Stripe payment failures by decline_code. Surface the top causes and the customers affected. Different decline = different fix.
#stripe#ecommerce#payments#customer-support - ops 1 minute · beginner
Stop noisy errors from paging you — in plain English
Suppress third-party SDK timeouts, ad-blocker errors, and other false-positives by describing them. No regex required.
#oncall#suppressions#sentry-alternative#saas - debugging 1 minute · intermediate
Find the cron that fails every Sunday at 3am
Bucket errors by hour-of-day and day-of-week to surface periodic failures hiding inside normal noise.
#cron#time-series#ops#infra