Hello
@ripe-application-70179
Your results match what I see. I reproduced your setup on an Ory Network project with opaque access tokens and zero grace, and got the same outcome.
quick answers:
• a used refresh token stays detectable for at least several days after it was used, not for the whole 30-day connection, and you can't configure that period.
• With zero grace, both simultaneous refreshes can return HTTP 200. The first access token works for about as long as one refresh takes, and it is already inactive by the time the second response arrives.
some notes for your use case:
• If the client keeps pair A, its next refresh presents a retired token. That triggers reuse detection, which revokes the chain including pair B, and the user has to reconnect. I confirmed this in testing. Clients should run only one refresh at a time per connection:
https://www.ory.sh/docs/hydra/debug#refresh-token-flow-fails
• When many requests compete, the second request can return 400 invalid_request instead of 200, with "Failed to refresh token because of multiple concurrent requests using the same token. Please retry the request." This didn't occur in my tests.
• If your MCP server caches introspection responses, it keeps accepting A's access token until that cache entry expires.
Let me know if anything here doesn't match what you see.