-
Notifications
You must be signed in to change notification settings - Fork 474
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
camunda:failedJobRetryTimeCycle lost on replace #1464
Comments
Updated with the current version, as it was already present in 3.2.2 |
Moving to backlog, as it is a known issue. |
This was referenced Aug 12, 2019
Closed via #1468. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
Making boundary events non-interrupting should keep all configured properties including
a configured
camunda:failedJobRetryTimeCycle
. The property is lost on replace though.Steps to Reproduce
camunda:failedJobRetryTimeCycle
is lostExpected Behavior
camunda:failedJobRetryTimeCycle
onEscalationEventDefinition
is kept on replaceEnvironment
v3.2.2
,v3.3.0-alpha.1
Depends on camunda/camunda-bpmn-moddle#48
The text was updated successfully, but these errors were encountered: