Camunda Operate stuck

Camunda 8 Topics
1

Hello All,

I am using self-managed Camunda version 8.5
and in the operate this error is thrown and the operate is stuck for long time and the new process instances doesn’t be fetched.

Exception occurred when performing post import for partition 1: Process instance is not yet imported for incident processing. Incident id: 2251799814427054, process instance id: 2251799814426979. Will be retried…

and as we debugged the Zeebe and Elasticsearch logs there is no error thrown in the logs.

exception
exception1343×402 20.6 KB

1 Like
2

Hi @Mohamed_Ahmed_Mohame , Even Im facing the same issue
If you have the solution, Please reply.
Couldn’t able to find the solution

2025-06-05 14:13:38.978 ERROR 905615 --- [   postimport_1] c.o.z.p.AbstractIncidentPostImportAction : Exception occurred when performing post import for partition 1: Process instance is not yet imported for incident processing. Incident id: 2251799877610115, process instance id: 2251799877610002. Will be retried...

io.camunda.operate.exceptions.OperateRuntimeException: Process instance is not yet imported for incident processing. Incident id: 2251799877610115, process instance id: 2251799877610002
	at io.camunda.operate.zeebeimport.post.elasticsearch.ElasticsearchIncidentPostImportAction.checkDataAndCollectParentTreePaths(ElasticsearchIncidentPostImportAction.java:609) ~[operate-importer-8.5.7.jar!/:8.5.7]
	at io.camunda.operate.zeebeimport.post.elasticsearch.ElasticsearchIncidentPostImportAction.searchForInstances(ElasticsearchIncidentPostImportAction.java:228) ~[operate-importer-8.5.7.jar!/:8.5.7]
	at io.camunda.operate.zeebeimport.post.AbstractIncidentPostImportAction.processPendingIncidents(AbstractIncidentPostImportAction.java:127) ~[operate-importer-8.5.7.jar!/:8.5.7]
	at io.camunda.operate.zeebeimport.post.AbstractIncidentPostImportAction.performOneRound(AbstractIncidentPostImportAction.java:64) ~[operate-importer-8.5.7.jar!/:8.5.7]
	at io.camunda.operate.zeebeimport.post.AbstractIncidentPostImportAction.run(AbstractIncidentPostImportAction.java:79) ~[operate-importer-8.5.7.jar!/:8.5.7]
	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-6.1.10.jar!/:6.1.10]
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
	at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
1 Like
3

I checked in the Camunda issues, for similar error, this was fixed[Operate post importer stops processing incidents · Issue #13189 · camunda/camunda · GitHub]

Would you please share your environment details like specific release, cluster details.

4

Im using Camunda 8.5.7 (Self managed)

5

Couldn’t find the solution in that thread

Im using Docker and not changed any default values

6

Are you using Docker or Helm Chart? Did you customize any values or using default values.

If you are using Helm chart, how many nodes/system are you using?

7

I am using Camunda v8.5.2 self managed with docker compose not with helm chart.

8

@Mohamed_Ahmed_Mohame Are you using Elasticsearch or Opensearch to store the data? Could you check the memory and storage including zeebe.

9

I tried to reproduce the error using docker compose, unfortunately, i was not able to produce.

Would you please share the VM details like CPU/memory/OS where the docker-compose.yaml is deployed.