In a non-automatonymous saga, I'm trying to do a simple aggregate (count) of some messages with a timeout, so I want to initiate the saga on the first message, after that I want the saga to orchestrate that same message.
I can't seem to find how to do this, InitiatedBy<T> doesn't work after the first message, and Orchestrates<T> doesn't initiate the saga.
It's fine if it retries on concurrency exceptions.
I figured this policy should work: NewOrExistingSagaPolicy, but I can't seem to find how to apply it to a basic saga.
I'm using MongoDb saga persistence.