Brainslug

@paescuj make sure to turn these points (https://github.com/directus/directus/pull/22412#issue-2282713563) into a proper review for others to verify / resolve

Feels related to https://github.com/directus/directus/issues/19664

This bug seems to be isolated to Chrome based browsers. And once you're pulling the tab out into a new window these can be considered 2 browsers (and looks like...

> They both have the same refresh token and arrive at the same point time, one updates the database with a new token, then the other request checks for a...

> The refresh in the second window uses the cookie that was set in the first window. If so then the second refresh shouldnt be failing as it would be...

> i'm theorizing it could be a regression from https://github.com/directus/directus/pull/22353 Thats not a regression but rather a security fix surfacing a deeper issue which was obscured by insecure handling of...

Leaving reference to this old discussion https://github.com/directus/directus/discussions/12788

This is an issue not a discussion / feature request, no need to upvote issues.

Can you try removing the `filter` property and checking again?

Besides these more advanced topic we shouldnt forget to add basic docs, telling people that this is even possible!