Fixed an issue with invoked service not being correctly started #1185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #1180
Problem was that for invoked services
action.activity.type
is always equal toxstate.invoke
and thus all invoked services were registered/deregistered under the same key instate.activities
, which led to a problem of an invoked service not being started when another invoked service has been stopped in following microstep because we only start services when machine settles macrostep to avoid starting services unnecessarily.cc @jschppll