OpsfluenceMSP Demo
Signed in asNorthern Edge IT·Toronto, ON·22 customers managed
← All incidents
Resolvedinc-1025·CCCopperfield Contractors·resolved 52m ago

Copperfield dispatch-app: error spike after deploy v4.19.0

GitHub deploy correlated within 4m with Sentry TypeError and Datadog SLO burn on Copperfield's dispatch-app. Rolled back in 24 min.
IMPACT
Copperfield · dispatch.copperfield.ca — ~1,100 failed job assignments
CORRELATED ACROSS
GGitHub AuditSySentryDdDatadogPPagerDutySSlack
View shareable post-mortem

Timeline

  1. GGitHub Audit·22:20·1h ago·workflows.completed
    Deploy to production · dispatch-app
    Commit c9f4a2 by rachel.wu merged to main and deployed via GitHub Actions. 14 files, 322 lines changed.
  2. SySentry·22:24·1h ago·issue.first_seen
    New issue: TypeError in dispatch.assignJob
    'Cannot read properties of undefined (reading foremanId)'. First seen on release v4.19.0. 411 events in 4 minutes.
  3. DdDatadog·22:25·1h ago·monitor.triggered
    Monitor: p99 latency /api/dispatch > 3s (10m)
    Latency spiked from 420ms to 4.8s after the deploy. Error rate jumped 0.2% → 11.6%.
  4. PPagerDuty·22:26·1h ago·incident.trigger
    PagerDuty page — Copperfield on-call
    SLO burn rate: 14x fast. On-call paged; ack in 2m.
  5. SSlack·22:27·1h ago·conversations.create
    Slack incident channel created — #copperfield-inc-1025
    Auto-invited on-call + rachel.wu (deploy author). Card links Sentry issue + Datadog dashboard + GitHub diff.
  6. GGitHub Audit·22:37·58m ago·workflows.dispatch
    Rollback deploy · dispatch-app → v4.18.3
    workflow_dispatch triggered by rachel.wu. Rollback deploy completed in 3m.
  7. DdDatadog·22:43·52m ago·monitor.resolved
    Monitor resolved: p99 latency /api/dispatch
    p99 back to 470ms. Error rate 0.3%. Recovery confirmed.