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.

Sign up for GitHub

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

Jump to bottom

updateEventTriggers is problematic in some scenarios #42

Open

tobiasschaefer opened this issue Feb 22, 2022 · 0 comments

Labels

bug

tobiasschaefer commented Feb 22, 2022

We have a message receive task with an attached timer boundary event. The timer is initialized with a transient process variable.

The migration fails every time if a token is on the message receive task because "updateEventTriggers" is enabled by default and the timer cannot be initialized due to the missing transient process variable.
We could switch to a persistent variable and it would work in our case because the timer is initialized with an absolute value. However, if it was a relative value the timer would start again with every migration. This would be wrong.

In both cases:
"updateEventTrigger" should be configurable in some way. Note: it is not sufficient to enable/disable it globally

tobiasschaefer added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment