When something goes wrong during the orchestration of a booking, it goes into the failed state. What's the recommended way to get that reservation out of that state after correcting the error? In the meantime the signal is up and running, so recreating the booking is not really an option, as that would mean they loose the signal again for some time.
Changing the "Service State" property on the reservation instance object is probably not sufficient, because the booking manager element is then not aware of the change?
Tom,
It is today possible to use the ApplyServiceState to retrigger LSO ( with an 'External' event that you can use to bypass the orchestration ) . If LSO execution succeeds, Service state will no longer be 'Failed'.
Do note BLC will still be in a failed state ...
We will review that use case (DCP194202) to make sure there an out of the shelve feature to leave both BLC and service state from failure state.