We were able to figure out the issue. The refresh token sequence was referencing old ids, so we just dropped all the refresh tokens and that solved it.

Was this happening by default or did you try to refresh the refresh token yourself?

It was happening by default. I think it's because we had to do a full DB migration. All the refresh tokens would've been copied over as well which I'm assuming caused the issue

Ok thanks for the info