Back to All Scenarios
PASSEDcloud / gcp_run
GCP: Cloud Run Service Failing — Container Startup Crash
A GCP Cloud Run service deployed a new revision that crashes on startup. All traffic routing to the failing revision.
Pattern
SERVER_ERROR
Expected: GCP_CLOUDRUN_CRASH
Severity
HIGH
Confidence
55%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | GCP_CLOUDRUN_CRASH | SERVER_ERROR | |
| Severity Assessment | CRITICAL | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
GCP Cloud Run service 'api'. New revision deployed with misconfigured env var. Container crashes in 2 seconds. Traffic routing: 100% to broken revision.
Injected Error Messages (1)
GCP Cloud Run crash — service 'api' new revision failing on startup, container exit code 1 within 2 seconds, env var DATABASE_URL missing, all traffic routed to broken revision, 503 on all requests
Neural Engine Root Cause Analysis
Server error detected — the application is returning 5xx errors, indicating a crash, unhandled exception, or backend failure.
Remediation Plan
Check application logs for unhandled exceptions. Restart the service if crashing. Review recent deployments for regressions.
Improvements Applied
- Pattern classified as SERVER_ERROR (expected GCP_CLOUDRUN_CRASH)
- Severity: HIGH (expected CRITICAL)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnr9bl09calig71vzk4crk