Camunda 7 Optimize Not Showing Data – Causes & Fixes (Production Guide)

 Introduction

A very common and confusing issue in Camunda 7 setups is:

❌ Camunda Optimize is running, but no data is visible

Typical symptoms

  • Optimize UI loads correctly

  • Dashboards show “No data available”

  • Reports remain empty

  • No obvious error in Optimize UI

  • Issue appears mainly after deployment or in production

👉 In most cases, Optimize is healthy, but data is not being imported correctly.

This blog explains:

  • How Optimize gets its data

  • Why data does not appear

  • The most common root causes

  • Clear fixes you can apply immediately

How Camunda Optimize Works (Quick Architecture)

Camunda Optimize does NOT read directly from the Camunda database.

Data flow

Camunda Engine
   ↓ (History API)
Optimize Importer
   ↓
Elasticsearch
   ↓
Optimize UI

👉 If any step fails, Optimize shows no data.

Root Cause #1: History Level Too Low (MOST COMMON)

Problem

Camunda engine history level is set to:

  • none

  • activity

Optimize requires FULL history.

How to check

In camunda.cfg.xml or application.yml:

<property name="history">full</property>

Fix

✔ Set history level to full
✔ Restart Camunda
✔ Wait for new data (history is NOT retroactive)

⚠️ Old instances will not appear if history was previously disabled.

Root Cause #2: History Cleanup Deleting Data

Problem

History cleanup is enabled with a very small TTL (e.g. 1–3 days).

Result

  • Data is deleted before Optimize imports it

  • Dashboards stay empty

Fix

✔ Increase TTL:

History Time To Live = 30–90 days

✔ Ensure cleanup runs after Optimize import

Root Cause #3: Optimize Importer Not Running

Problem

Optimize application is running, but importer threads are stopped.

How to check logs

Look for:

import finished successfully

Or errors like:

Cannot fetch historic process instances

Fix

✔ Check Optimize logs
✔ Verify engine REST endpoint
✔ Restart Optimize service

Root Cause #4: Optimize Not Connected to the Correct Engine

Problem

Optimize is pointing to:

  • Wrong Camunda engine URL

  • Wrong REST API endpoint

  • Wrong credentials

Check environment.yml

engines:
  - name: camunda-engine
    rest: http://camunda:8080/engine-rest

Fix

✔ Validate REST URL
✔ Test /engine-rest/engine manually
✔ Ensure credentials are correct

Root Cause #5: Elasticsearch Issues

Problem

Elasticsearch is:

  • Not running

  • Running but read-only

  • Out of disk space

  • Version incompatible

Symptoms

  • Optimize UI loads

  • No data stored

Fix

✔ Check Elasticsearch health:

GET /_cluster/health

✔ Ensure:

  • Disk not full

  • Indices writable

  • Supported version

Root Cause #6: Optimize Version Mismatch

Problem

Camunda engine and Optimize versions do not match.

Example:

  • Camunda 7.18

  • Optimize 7.14

Fix

✔ Always align versions:

Camunda 7.x  ⇄  Optimize 7.x (same minor version)

Root Cause #7: Optimize Importing Only New Data

Problem

Optimize does not import old history automatically.

Result

  • Existing completed processes do not appear

  • Only new instances after Optimize start are visible

Fix

✔ Restart Optimize with import enabled
✔ Accept that old data may not appear
✔ Plan Optimize deployment early in project lifecycle

Debug Checklist (Step-by-Step)

  1. Check Camunda history level = full

  2. Verify new processes are completing

  3. Check Optimize logs (importer status)

  4. Verify REST engine URL

  5. Check Elasticsearch health

  6. Validate version compatibility

  7. Check history cleanup TTL

  8. Wait for import cycle (not instant)

Production Best Practices

✔ Enable history from day one
✔ Use TTL ≥ 30 days
✔ Monitor Optimize importer logs
✔ Monitor Elasticsearch disk usage
✔ Keep Camunda & Optimize versions aligned
✔ Do NOT expect Optimize to show old data magically
✔ Validate Optimize after every deployment

Common Anti-Patterns 🚨

❌ History level = activity
❌ Very small TTL (1–2 days)
❌ Deploy Optimize months later
❌ Ignoring Elasticsearch health
❌ Version mismatch
❌ Expecting instant dashboards

Interview Question (Very Common)

Q: Why is Optimize empty even though processes are running?
A: Because Optimize depends on FULL history + importer + Elasticsearch, and one of them is misconfigured.

Conclusion

If Camunda 7 Optimize shows no data, the problem is almost always:

  • history disabled

  • importer not running

  • Elasticsearch issue

  • wrong configuration

  • version mismatch

👉 Optimize is not real-time BI — it depends entirely on correct history and imports.

Fix the pipeline, and the data appears.

💼 Professional Support Available

If you are facing issues in real projects related to enterprise backend development or workflow automation, I provide paid consulting, production debugging, project support, and focused trainings.

Technologies covered include Java, Spring Boot, PL/SQL, Azure, and workflow automation (jBPM, Camunda BPM, RHPAM).

📧 Contact: ishikhanirankari@gmail.com | info@realtechnologiesindia.com

🌐 Website: IT Trainings | Digital metal podium     

Comments

Post a Comment

Popular posts from this blog

jBPM Installation Guide: Step by Step Setup

  jBPM Installation Guide – Step by Step for Beginners If you are starting with jBPM (Java Business Process Management) , the first step is to set up your environment. In this guide, we’ll walk through how to install jBPM, configure it, and run your first business process. 🔎 What is jBPM? Before we dive into installation, a quick recap: jBPM is an open-source Business Process Management (BPM) suite , written in Java, that allows you to model, execute, and monitor workflows using BPMN 2.0 standards. It can run standalone , embedded in applications , or deployed on a Java EE server . 🖥️ Prerequisites Before installing jBPM, make sure you have: Java JDK 11 or later (Java 17 is commonly used) Maven 3.x (for building and managing dependencies) Git (optional, if you want to clone sample projects) A Database (H2, MySQL, PostgreSQL, or Oracle) – jBPM ships with H2 for testing At least 4GB RAM (8GB recommended for Workbench & KIE Server) 📦 Download ...
Read more

Scopes of Signal in jBPM

Image
💡 Introduction Signals in jBPM 7 are a core part of event-driven workflow design. They allow asynchronous communication between process instances, making it possible to start , interrupt , or coordinate processes without direct linking. However, signals can have different scopes , which define how far the signal travels and who receives it . Let’s explore the four available scopes in detail: 🔹 Process Scope 🔹 Default Scope 🔹 External Scope 🔹 Project Instance Scope 🧩 1️⃣ Process Scope 📘 Definition Process scope signals are local to a single process instance or its child subprocesses . They are not visible outside that instance hierarchy. 📋 Use Case Used for communication inside the same process , like triggering subprocesses or event sub-processes. 🖼️ Process Scope Example Below is an example of a simple process-scoped signal. Only this process (or its subprocess) will catch this signal. ⚙️ 2️⃣ Default Scope 📘 Definition The default scope ...
Read more

OOPs Concepts in Java | English | Object Oriented Programming Explained

Image
🔹OOPS (Object Oriented Programming System) in Java Object-Oriented Programming (OOPS) is a programming paradigm that uses classes and objects to design software. It simplifies development and maintenance by applying key concepts: 📌 Class: Class   is a user-defined data type which defines its properties and its functions. Class is the only logical representation of the data. For example, Human beings in an organisation is a class like Employee. The age, name, department, salary etc. of a human being/employee are its properties, and the jobs performed by the employees in an organisation are known as functions.  The class does not occupy any memory space till the time an object is instantiated. A class is a user-defined data type that defines properties and functions. For example: Class: Employee Properties: name, age, salary Functions: work(), attendMeeting() A class does not occupy memory until an object is created. ...
Read more