Incidents doesnt export in Operate Camunda 8.8

Camunda 8 Topics
1

After update to Camunda 8.8 incidents doesnt export in Operate. In orchestration cluster logs i see this error:

[2025-10-25 12:16:03.833] [exporter-camundaexporter-p1-tasks-0] WARN
        io.camunda.zeebe.broker.exporter.camundaexporter - Error occurred while performing a background task Incident update task; error message Failed to fetch incidents associated with post-export updates; it's possible they are simply not visible yet. Missing incident IDs: [[2251799814194183, 2251799814191647, 2251799815222703, 2251799815222360, 2251799815081558, 2251799815221197, 2251799814194908, 2251799816117502, 2251799815081464, 2251799815220986]]; operation will be retried
java.util.concurrent.CompletionException: io.camunda.zeebe.exporter.api.ExporterException: Failed to fetch incidents associated with post-export updates; it's possible they are simply not visible yet. Missing incident IDs: [[2251799814194183, 2251799814191647, 2251799815222703, 2251799815222360, 2251799815081558, 2251799815221197, 2251799814194908, 2251799816117502, 2251799815081464, 2251799815220986]]
        at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source)
        at java.base/java.util.concurrent.CompletableFuture.uniApplyNow(Unknown Source)
        at java.base/java.util.concurrent.CompletableFuture.uniApplyStage(Unknown Source)
        at java.base/java.util.concurrent.CompletableFuture.thenApplyAsync(Unknown Source)
        at java.base/java.util.concurrent.CompletableFuture.thenApplyAsync(Unknown Source)
        at io.camunda.exporter.tasks.ReschedulingTask.run(ReschedulingTask.java:64)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
Caused by: io.camunda.zeebe.exporter.api.ExporterException: Failed to fetch incidents associated with post-export updates; it's possible they are simply not visible yet. Missing incident IDs: [[2251799814194183, 2251799814191647, 2251799815222703, 2251799815222360, 2251799815081558, 2251799815221197, 2251799814194908, 2251799816117502, 2251799815081464, 2251799815220986]]
        at io.camunda.exporter.tasks.incident.IncidentUpdateTask.getPendingIncidentsBatch(IncidentUpdateTask.java:642)
        at io.camunda.exporter.tasks.incident.IncidentUpdateTask.processNextBatch(IncidentUpdateTask.java:134)
        at io.camunda.exporter.tasks.incident.IncidentUpdateTask.execute(IncidentUpdateTask.java:93)
        at io.camunda.exporter.tasks.ReschedulingTask.run(ReschedulingTask.java:53)
2

Hi @Bantexx,

Thank you for reporting this issue. I can see you’re experiencing a problem with incident export to Operate after upgrading to Camunda 8.8.

Issue Classification

This appears to be a Problem - incidents are not being exported to Operate as expected after the upgrade, which is broken functionality.

Analysis

The error you’re seeing indicates that the IncidentUpdateTask is failing to fetch incidents that should be visible during post-export updates. The specific error message:

Failed to fetch incidents associated with post-export updates; it's possible they are simply not visible yet. Missing incident IDs: [...]

This suggests there may be a synchronization issue between the incident creation/update process and the export visibility in Camunda 8.8.

Troubleshooting Steps

While I couldn’t find this specific issue documented in our knowledge base, here are some steps to help diagnose and potentially resolve the problem:

1. Check Elasticsearch/OpenSearch Health

  • Verify your Elasticsearch/OpenSearch cluster is healthy (status should be green)
  • Check that all required indices exist and are accessible (operate-*, zeebe-*)
  • Look for any index corruption or failed shards

2. Review Configuration

  • Ensure your exporter configuration is compatible with Camunda 8.8
  • Verify that index prefixes and exporter settings are correct after the upgrade
  • Check if there were any configuration changes needed for 8.8 that might have been missed

3. Check Component Logs

  • Review Zeebe broker logs for additional exporter errors
  • Check Operate logs for import/processing errors
  • Look for any resource bottlenecks or memory issues

4. Verify Data Flow

  • Check if new incidents are being created and if the issue affects all incidents or just specific ones
  • Verify if other data (process instances, tasks) are being exported correctly

Potential Bug Report

Since this appears to be a specific issue with Camunda 8.8 that isn’t documented in our knowledge base, this might be a new bug introduced in the 8.8 release. I’d recommend:

  1. Filing a GitHub issue at: GitHub · Where software is built
  2. Include the following information:
    • Camunda version: 8.8
    • Environment: Self-Managed (I assume based on your logs)
    • Complete error logs (which you’ve already provided)
    • Steps that led to the issue (upgrade from previous version)
    • Expected vs actual behavior

Additional Information Needed

To better assist you, could you please provide:

  • What version did you upgrade from?
  • Are you running Self-Managed or SaaS?
  • Are other components (process instances, tasks) exporting correctly?
  • Any recent configuration changes made during the upgrade?

This will help determine if this is a widespread issue or specific to your setup.

References:

Let me know if you need help with any of these troubleshooting steps or if you discover additional information!

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.