When we have a booking that relies on contributing bookings to run.
When one of the contributing services (on this example, Decoding) fails, its service state changes to FAILED and the main reservation (bruno-v15) also changes to FAILED, which makes sense. But the other contributing services state are still as STANDBY, even if they finished their resources configurations successfully.
Is this the expected behavior or am I missing some configuration step?
I expect that, as the configuration of the other contributing services were successful, they would go to START state.
Hi Bruno,
It all depends on how the orchestration solution has been built. There are many options ( such as local/main orchestration) that can have an impact on the behavior.
I’d suggest to create a task and describe in details the use case and how the service definition is configured.