Skip to content
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

Significance of running engines after processes end #42

Closed
MaheshkumarSundaram opened this issue Aug 31, 2022 · 1 comment
Closed

Significance of running engines after processes end #42

MaheshkumarSundaram opened this issue Aug 31, 2022 · 1 comment

Comments

@MaheshkumarSundaram
Copy link

MaheshkumarSundaram commented Aug 31, 2022

Hi,

I could see that there are running engines in the Workbench UI after the processes end.
If I start processes, after their end events; I suppose there should no running engines right?
But I still see two running instances (in case of 2 processes) after their end events.

Could you please explain the significance behind this?

Aside from the above question, is the data.caseId unique across all instances?

Thanks!

@ralphhanna
Copy link
Collaborator

There is no real impact other than memory, and no real value of keeping them.

Therefore, in release 1.3.3 it removes completed engines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants