-
Notifications
You must be signed in to change notification settings - Fork 167
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
Multiple executions of the same engine at the same time. #151
Comments
One engine handles one execution. A definition may start multiple processes, e.g. a multi-instance call activity. |
Thanks for responding. If the process represents the on-boarding of customers for example. You'd model it as a single execution that can respond to events about the need for a new customer and then invoke the "onboard a single customer" activity? If so, the list of postponed things can include the same task multiple times? How might you associate a postponed task with the customer that it represents? Do you bake in the customer info into every message that traces back to their on-boarding event? Sorry for the n00b questions. |
Any update on how to do such scenario efficiently. I'm in a similar situation for a workflow management tool. |
I have started project called |
If I set up a service that invokes a process on demand, can multiple executions of a process be running on the same engine at the same time or do I need to create an Engine per execution?
Thank you.
The text was updated successfully, but these errors were encountered: