-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploying Workflow definition throws error #3278
Comments
The error is caused by an unknown extension <bpmn:endEvent id="EndEvent_0th2j52">
<bpmn:extensionElements>
<zeebe:payloadMappings>
<zeebe:mapping source="sourceValue" target="targetValue" type="PUT" />
</zeebe:payloadMappings>
</bpmn:extensionElements>
<bpmn:incoming>SequenceFlow_139z5p7</bpmn:incoming>
</bpmn:endEvent> It seems that the modeler creates an outdated extension element for the variable mappings. However, we should improve the error message 😅 |
I opened an issue for the modeler: zeebe-io/zeebe-modeler#138 |
@saig0 @jwulf Hi. I got a similar error when trying to deploy a very simple bpmn. Did not have payloadMapping in my case. BPMN:
Running zeebe-modeller 8.0 with 0.22 version of zeebe, 0.22.0-alpha.5 version of node client |
@tvvignesh, this is not the same issue. In your example, the deployment is rejected because your BPMN is not valid. In the original case, an exception was thrown in the model API because of a bug. As mentioned in the rejection failure message: the start event (id: "StartEvent_1") have a message event definition (i.e. it's a message start event) but it does not refer a message. In the Zeebe modeler, you need to select the message start event and select (or create) a message in the properties panel. |
@saig0 Oops. You are right. Found the error and fixed it. Sorry for the confusion. |
Describe the bug
Deploying the attached BPMN diagram on SNAPSHOT and 0.21.1 throws an error.
Expected behavior
Workflow definition deploys.
Log/Stacktrace
Full Stacktrace
await-outcome.bpmn.zip
Environment:
The text was updated successfully, but these errors were encountered: