Camunda Cockpit Shows Incident but No Error – Root Cause & Solution
In Camunda 7 , Cockpit incidents are meant to help operators quickly identify failures in running processes. However, a confusing and very common production issue is: ❌ Camunda Cockpit shows an Incident, but no clear error message or stack trace is visible. This blog explains why this happens , how to trace the real root cause , and practical solutions used in enterprise projects. 1️⃣ What Is an Incident in Camunda? An incident is created when: A job execution fails Retries reach 0 The engine cannot continue process execution Incidents are typically linked to: Failed service tasks External tasks Timers Asynchronous continuations 2️⃣ Why Cockpit Shows Incident but No Error đź”´ Root Cause 1: Exception Occurred Earlier, Not in Current Step Camunda only displays the last known failure , not always the original exception . đź“Ś The real error may have occurred: In a previous async step In an earlier delegate execution During a retry attempt ✅ Solution : Check History → Incidents Revi...