Falko Menge

Instead of splitting the importers into a separate deployment, we could configure each replica's importer to work on a different chunk of data. However, that would likely require a stateful...

@jothikiruthika FYI

@mustafadagher Either of the following feature requests would be a solution for the customer to "send data with an Error Throw Event": - Preferred: https://github.com/camunda/zeebe/issues/13940 - Workaround: https://github.com/camunda/zeebe/issues/11459 (here we...

Urgency is medium. It can be worked around by throwing more hardware at the problem, but the hardware budget for this customer is already quite high

@jothikiruthika will investigate if a [multi-instance completion condition](https://docs.camunda.io/docs/next/components/modeler/bpmn/multi-instance/#completion-condition) could solve it for her customer.

We just discussed this in today's Camunda Cloud Family Get-Together and the answer is **yes**. We agreed that it would make sense to improve documentation and maybe even add a...

This issue has been raised by an Enterprise customer in SUPPORT-11857 and @ikheraj17 and I also stumbled over it when migrating a CP project to CC.

@christinaausley I don't have more time to work on this. Primarily, I wanted to report the documentation issue. Could your team please finish the versioned docs? This may also need...

@npepinpe The stable branches should work, right? https://github.com/camunda/zeebe/tree/stable/8.5/zeebe/exporters/elasticsearch-exporter/src/main/resources

Then a combination of linking to stable branches for maintained versions and to the last release tag for older unmaintained versions would work.