Child service version switches mid-calculation #741
Description
Bug report
What is the current behavior?
In long-running calculations that involve multiple invocations of a single child service, the calculation incorrectly (I can't think of a scenario where this is the right behavior) switches to a newer default version of the child service if one is released during the calculation. The initial n calls to the child service use Version 1 (V1), but the subsequent calls use the new Version 2 (V2). This version inconsistency leads to unreliable and inconsistent results and must be prevented.
What is the expected behavior?
The parent process should lock the version of all child services to the default version present at the start of the calculation. This ensures consistent results.