Timeout.AnyReceived not handled in Initial saga state

[Alexey Zimarev]

I am getting strange errors from Automatonynmous state machine saga:

The IdleTimeoutDev.AnyReceived event is not handled during the Initial state for the TripSaga state machine

How does this work exactly? I am expecting IdleTimeout to be correlated to some saga but how can it be received in saga initial state? In this state there is no saga persisted, how MT binds them?

[Chris Patterson]

It seems like you're getting a scheduled message delivered to a saga that doesn't exist. Either the correlation in the scheduled message is incorrect, or you aren't unscheduling the message early enough.

In the latter case, it is okay to configure the event to ignore the event in an Initial state using the OnMissingInstance() method within the Event(() => MyEvent) configurator. Of course this can be hard to access within a Schedule(), since it's buried under the covers. Perhaps I should make this the default behavior, or somehow make it configurable.

Either way, look for reasons why you'd be getting the scheduled message without a valid existing correlated saga instance.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/12c6df66-24a8-4f56-928b-199922530cd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.