@haighis Yep, I've been wrapping my head around this one too. I was going the persistent actor route as well, but you can't do it with sql server in my case because the external resource is the database. So it would have to be some other store. We use couchbase as a cache server, and so I was thinking of use that some how. But if that were the case I'd have to build that out as they don't have a persistent store for couchbase yet. So for now I've decided to store up to a certain time limit (I'll change the time limit to a bounded limit once it's implemented) and then I'm just going to fail the actor. That will free up the memory, but will reset everything and we'll just keep reloading messages over again.