In my usecase, my start saga generates a list of events to be consumed by external microservice (worker). Once an event is done the worker generates an event.
My listener is able to listen to those events, Is there a way saga can listen to those events directly instead of having a listener in between.
So that once the saga gets the necessary event it can then end that saga based on the business logic.
Run Report 1
Run Report 2
Run Report 3
So once the saga receives all 3 reports completed event then the saga will end.