Reuben Bond

@Rikarin are you still seeing this issue? I believe that this should work in Orleans v7.x and later. If there is an issue here, please let us know.

It would need to be a re-implementation, unfortunately, since 3.x uses a completely different code generator.

Where are the requests for this system originating from? It's interesting that the grains are being activated at all if there are no requests being sent their way, since grains...

Does this repro on 7.2.1? Do you have a custom directory?

Oh, are you attempting to perform a rolling upgrade from 3.x to 7.x? That is not supported - the two versions are not wire compatible

Does that error only occur during rolling deployment, @tiasmt, i.e., is the error resolved after deployment completes? This is expected, to a degree, while the grain directory is in flux...

Are you using a custom serializer (eg, JSON)? I'm looking for the source of the bug now - thank you for bearing with me. What seems to be happening is...

Do you still have the same exception message as [above](https://github.com/dotnet/orleans/issues/8667#issuecomment-1768328260)? i.e: ``` Error processing cluster membership updates exceptions.Message: Argument must have a previous version to the current instance. Expected

Are you able to share logs? If you prefer not to upload them here, we could share them via email instead

@tanordheim this looks like a different issue to me - the Redis timeout is the likely cause. It may be worth opening a new issue with details