-
## Introduction
We want to transform the Zeebe Java Client into a more generic Camunda Java Client, in order to support not only `Zeebe` but also other products (eg. Operate, Tasklist). Allowin…
-
**Describe the bug**
Output mappings are not correctly propagated throughout the instances of multi instance body leading to incorrect output.
**To Reproduce**
Consider the following ex…
-
**Describe the bug**
```
Expected to process record 'TypedRecordImpl{metadata=RecordMetadata{recordType=COMMAND, valueType=DEPLOYMENT, intent=CREATE}, value={...}' without errors, but exception oc…
-
### Describe the bug
Applying this template causes an error to be thrown:
```json
{
"$schema": "https://unpkg.com/@camunda/zeebe-element-templates-json-schema/resources/schema.json",
"name"…
-
**Description**
Currently, the `CamundaExporterHandlerIT` test cases break if more than one `ExporterHandler` implementation is used within a test case.
As a result, `update` and `delete` ex…
-
**Describe the bug**
It seems right now errors that occur during flush in Raft are uncaught, and end up causing the partitions to go inactive. This mostly occurs when running Zeebe with an NFS file…
-
The setting zeebe.client.requestTimeout must be used as a constant for ActivateJobs requests, but it internally changed by ZeebeSourceTaskFetcher based on backoff algorithm.
This causes many unproces…
-
**Description**
After last weeks release, release benchmarks are broken for versions 8.4.x, 8.3.x and 8.2.x.
Preliminary Investigation:
Brokers are running, but gateway pods are not getting re…
-
**Describe the bug**
When an error occurs during job execution, the `elementId` (which usually contains the flowNodeId) of the job record gets overwritten with `NO_CATCH_EVENT_FOUND`:
https://gi…
-
**Describe the bug**
`PendingProcessMessageSubscriptionChecker` can't schedule itself because `scheduleService` is null.
**To Reproduce**
Unclear
**Expected behavior**
No NPE
**Log/S…