Operate Importer: ignore missing parent error

Camunda 8 Topics Discussion & Questions
1

Hi, we are using operate with camunda cloud (zeebe). For some reason we lost some historical zeebe indices and now operate importer is stuck with this error

│ 2022-09-28 07:08:49.308 ERROR 8 --- [       import_2] i.c.o.z.ImportJob                        : Unable to find parent tree path for flow node instance id 2251800405915259           │
│ io.camunda.operate.exceptions.OperateRuntimeException: Unable to find parent tree path for flow node instance id 2251800405915259                                                     │
│     at io.camunda.operate.zeebeimport.v1_3.processors.FlowNodeInstanceZeebeRecordProcessor.getParentTreePath(FlowNodeInstanceZeebeRecordProcessor.java:177) ~[operate-importer-1_3-1. │
│     at io.camunda.operate.zeebeimport.v1_3.processors.FlowNodeInstanceZeebeRecordProcessor.updateFlowNodeInstance(FlowNodeInstanceZeebeRecordProcessor.java:125) ~[operate-importer-1 │
│     at io.camunda.operate.zeebeimport.v1_3.processors.FlowNodeInstanceZeebeRecordProcessor.processProcessInstanceRecord(FlowNodeInstanceZeebeRecordProcessor.java:103) ~[operate-impo │
│     at io.camunda.operate.zeebeimport.v1_3.processors.ElasticsearchBulkProcessor.processProcessInstanceRecords(ElasticsearchBulkProcessor.java:167) ~[operate-importer-1_3-1.3.7.jar! │
│     at io.camunda.operate.zeebeimport.v1_3.processors.ElasticsearchBulkProcessor.processZeebeRecords(ElasticsearchBulkProcessor.java:80) ~[operate-importer-1_3-1.3.7.jar!/:?]        │
│     at io.camunda.operate.zeebeimport.AbstractImportBatchProcessor.performImport(AbstractImportBatchProcessor.java:27) ~[operate-importer-common-1.3.7.jar!/:?]                       │
│     at io.camunda.operate.zeebeimport.ImportJob.processOneIndexBatch(ImportJob.java:116) ~[operate-importer-1.3.7.jar!/:?]                                                            │
│     at io.camunda.operate.zeebeimport.ImportJob.call(ImportJob.java:80) ~[operate-importer-1.3.7.jar!/:?]                                                                             │
│     at io.camunda.operate.zeebeimport.RecordsReader.lambda$scheduleImport$2(RecordsReader.java:249) ~[operate-importer-1.3.7.jar!/:?]                                                 │
│     at java.util.concurrent.FutureTask.run(Unknown Source) [?:?]                                                                                                                      │
│     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]                                                                                                        │
│     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]                                                                                                       │
│     at java.lang.Thread.run(Unknown Source) [?:?]

We don’t care about the lost data, but is there an option to juste ignore this event and carry on ?

2