Camundaa 8.8 incidents doesnt display in Operate

Camunda 8 Topics
, ,
2

Hello @Bantexx,

This appears to be a known issue with Camunda 8.8 after upgrading from 8.7. Based on your error logs and symptoms, you’re encountering a bug in the incident export/processing system that affects several users after the 8.7 → 8.8 upgrade.

Classification: Problem/Bug

Your issue matches a documented pattern where:

  • Incidents remain in PENDING status in Elasticsearch
  • Incidents are not visible in Operate UI
  • IncidentUpdateTask throws NullPointerException in the Camunda exporter logs
  • This specifically occurs after upgrading from 8.7 to 8.8

Immediate Steps You Can Try

1. Verify Migration Setup

Ensure your 8.7 → 8.8 migration was completed correctly:

  • Importer: The importer should have been left enabled until all 8.7 records were fully imported before relying solely on the Camunda Exporter
  • Index Prefixes: If you used custom index prefixes in 8.7, verify you ran the prefix-migration tool and configured consistent prefixes for both secondary storage and the Camunda Exporter:
    CAMUNDA_DATA_SECONDARYSTORAGE_*_INDEXPREFIX=<your-prefix>
ZEEBE_BROKER_EXPORTERS_CAMUNDA_ARGS_CONNECT_INDEXPREFIX=<your-prefix>

2. Check Elasticsearch Health

  • Verify cluster health and that all indices are green
  • Confirm both operate-* and harmonized indices are present and accessible

3. Temporary Mitigation for Stuck Post-Processing

If Operate’s post-processing is stuck due to missing data, you can temporarily set:

CAMUNDA_OPERATE_IMPORTER_POSTIMPORTERIGNOREMISSINGDATA="true"

This allows Operate to continue processing despite missing incident/process instance data.

Next Steps - File a Bug Report

Since this matches a known pattern of 8.8 incident export issues without a definitive fix, I recommend filing a GitHub issue with the following details:

Repository: GitHub · Where software is built

Include:

  • Exact Camunda versions (Zeebe, Operate, exporter versions)
  • Upgrade path (specific 8.7.x to 8.8.x versions)
  • Complete stack traces from your logs
  • Your exporter and secondary-storage configuration
  • Elasticsearch/OpenSearch health status
  • Index prefix configuration (if using custom prefixes)

References

This appears to be a product bug rather than a configuration issue, so escalating to the development team with detailed information will be the most effective path to resolution.

Let me know if you need help gathering any of the diagnostic information for the bug report!