I'd had a long running problem using multiple rooms whereby a newly created room would just suddenly disappear. After a lot of attempts to find out why, using a Codex agent to examine the River codebase, it appears that it is possible for old delegates to overwrite the current latest delegate in some situations. This seems to be because the delegate migration path is followed repeatedly under various situations, such as a page refresh, and if a response to retrieving an older delegate somehow arrives after a response for the latest active delegate, then it will overwrite the newer delegate as part of the migration flow.
I suspect this is becoming more of a problem for me because I have a long running/lived node that it likely pulling many old delegates over many versions of River. I'd rather not have to keep wiping my old nodes every time a new version of River comes out just to avoid this.
I'd had a long running problem using multiple rooms whereby a newly created room would just suddenly disappear. After a lot of attempts to find out why, using a Codex agent to examine the River codebase, it appears that it is possible for old delegates to overwrite the current latest delegate in some situations. This seems to be because the delegate migration path is followed repeatedly under various situations, such as a page refresh, and if a response to retrieving an older delegate somehow arrives after a response for the latest active delegate, then it will overwrite the newer delegate as part of the migration flow.
I suspect this is becoming more of a problem for me because I have a long running/lived node that it likely pulling many old delegates over many versions of River. I'd rather not have to keep wiping my old nodes every time a new version of River comes out just to avoid this.