Post-incident wrap-up #68
The most recent tracked incident was a positive warning alert triggered by sustained conditions. Across the visible window, the game added 61 reviews, the current 1-hour directional delta sits at 52, and the incident peak reached 52 in 1 hour. 1 earlier incident have already resolved.
Incident opened Apr 14, 2026, 9:15 AM and resolved Apr 14, 2026, 9:57 AM.
Peak tier reached: WARNING.
Reported score change during incident window: 0.0%.
Estimated time to peak: -361 m.
Estimated time to resolve: 42 m.
Before / after
Window from Apr 14, 2026, 3:14 AM to Apr 14, 2026, 9:56 AM.
Score before
86.0%
Score now
86.0%
Change
0.0%
Reviews added
61
Peak velocity
11/h
Composite impact score
low (15)Tier severity
+14
Review volume delta
+1
Peak velocity
+0
Score movement
+0
Resolution duration
+0
Likely cause ranking
Probabilities are heuristic and derived from approved tag assignments, classifier confidence, and editorial overrides.
100%
Sustained positive flow indicates sentiment recovery.
Incident FAQ
Auto-generated summary designed for quick sharing, operations handoffs, and SEO-friendly incident context.
What happened?
Graveyard Keeper entered a positive warning incident with 61 additional reviews in the tracked window.
How severe was it?
Incident remained in warning severity without crossing critical threshold. Composite impact score is 15/100 (LOW).
What are the most likely causes?
Positive Turnaround 100%
Is it resolving?
Resolved after 42 m with stabilized current sentiment state.
How far did sentiment move from normal?
Score moved by 0.0 points, from 86.0% to 86.0%. Peak velocity reached 11 reviews/hour.
Does it resemble a broader cluster?
No related incidents were detected across connected titles in the current comparison window.
External trigger timeline
Correlates model milestones with seasonal overlap and cause evidence to explain likely trigger context.
Apr 14, 2026, 3:14 AM
Peak pressure window
Peak tier reached WARNING.
Apr 14, 2026, 9:15 AM
Incident opened
Model opened a positive warning incident via sustained trigger logic.
Apr 14, 2026, 9:15 AM
Likely cause: Positive Turnaround
Sustained positive flow indicates sentiment recovery. (alerts.trigger_type)
Apr 14, 2026, 9:56 AM
Baseline divergence
1h direction velocity ran at 157.58x slot baseline.
Apr 14, 2026, 9:57 AM
Incident resolved
Incident exited alert thresholds and moved to resolved state.
Recovery tracking
Forecast ETA to normalize sentiment: Now (LOW confidence)
Velocity is already within the stabilization band, so sentiment appears normalized.
Not enough post-resolve snapshot history yet — metrics will fill in as data accumulates.
Time to peak
-361 m
Time to resolve
42 m
Score at start
86.0%
Score at peak
86.0%
Uplift
0.0 pt
Recovered +24 h
n/a
Recovered +7 d
n/a
Recovered +30 d
n/a
Sentiment stabilised
Yes
Alert timeline
Escalation history across active and resolved incidents for this game.
Started Apr 14, 2026, 9:15 AM
Opened at warning severity
Apr 14, 2026, 9:14 AM
Trigger: sustained
Peaked at warning severity
Apr 14, 2026, 9:34 AM
Resolved from warning severity
Apr 14, 2026, 9:56 AM
