RTC: Disconnection dialog "Retry" no longer works after nonce expires

[alecgeatches]

I just returned to a post that has been idling in a tab for a dayish and attempts to retry are producing 403s as shown below:

Screen.Recording.2026-03-04.at.12.06.12.PM.mov

POST /index.php?rest_route=%2Fwp-sync%2Fv1%2Fupdates&_locale=user HTTP/1.1

HTTP/1.1 403 Forbidden
{
    "code": "rest_cookie_invalid_nonce",
    "message": "Cookie check failed",
    "data": {
        "status": 403
    }
}

I thought apiFetch would automatically refresh the REST nonce but it doesn't appear to be doing so.

[Mamaduka]

The apiFetch should refresh the nonce if the rest_cookie_invalid_nonce error is returned. There are some edge cases we haven't resolved yet, like partially corrupted cookies. See the discussion in #71458. cc @jsnajdr

For testing purposes, you could give nonces a shorter lifespan:

add_filter( 'nonce_life', function() { return 60; } );

[TaisaDesigner]

Hi,

I just installed the beta and was trying it on a tests site, and this message appears to me all of the time. Specially when I go and go back and forth into "revisions" but also while editting, not even iddle.
Retry doesn't help. I searched and found this post.

Happens with no plugins active, both with Astra and Twenty-twentyfive themes. Posts with almost no content.

Also I am the only admin... shouldn't this collaboration feature be inactive if no one else can even be "working" at the same time?
Is it even possible to disable it? I am also worried about performance.
Edit: I found there is indeed an option... Why is this enabled by default, or only on beta?

[alecgeatches]

@TaisaDesigner I'm glad you found the option! It was changed to be enabled by default on WordPress 7.0 beta 3 as we increase testing. For anyone else who may be locked out of posts due to this error, collaborative editing can be enabled or disabled via:

WordPress Admin → Settings → Writing → "Enable real-time collaboration" checkbox:

---

I can't replicate your revisions issue specifically, but we'll continue to look into it!

[jsnajdr]

The apiFetch should refresh the nonce if the rest_cookie_invalid_nonce error is returned.

The reason why this happens is quite straightforward: the relevant apiFetch call uses parse: false, and then all the automated checks are disabled. Fixing in #76283.