We are having an issue with unscheduling expired scheduled messages in sagas:
When a scheduled message is received and the saga triggers an Unschedule action on the same Schedule it wrongly sends a CancelScheduledMessage. I think this is caused by this line:
Here the TokenId is set to default(Guid?) which equals new Guid?(). I'm assuming the token should be reset to null to prevent any activity until the message is scheduled again. The same code is here in the UnscheduleActivity:
I am not sure if this is intended behaviour?
Our quick fix for now is the simply not call Unschedule on a received scheduled message.