Thanks for reporting this here. Off hand, I do notice you’re using an outdated endpoint so you may want to update that to a current version.
The mutation itself is correct though so I don’t see the version causing issues here. Do you by chance have the x-request-id from the mutation where it resulted in unexpected behavior?
Also, is this happening on a single shop or are you noticing this happening across multiple shops? How frequently do you notice this happening?
I’ve got three x-request-id from two different accounts:
Account A (failed request): 93678c3b-45a0-4ab3-bae2-28024f66fa05-1752485222
Account B (failed request): 216162c0-cd4b-4790-9255-aaba5f76136b-1752488672
Account B (successful request): ee1b8da2-c403-4e6c-9c85-799da8c0d688-1752488904
These were requests to reset the password and uses 2025-07 version. They both exhibit issue where the link in the email redirects to /account/invalid_token.
It’s happening on a single shop (I don’t have any other stores to compare it to). I don’t have any data on the frequency across different users, but at least with the Account A above, it seems to consistently result in one of the issues I mentioned in the initial post.
Yeah I saw the link back to my post. I think I’ll be discussing my issue via a support ticket now, but I’ll keep this thread updated. Hopefully we can get it solved soon!
Mine doesn’t seem consistent between accounts. Account A I mentioned above seems to consistently have a problem. Account B has had random issues where the link wouldn’t be clickable (maybe about 2/3 times it would work), but for the first time when I tested to get the x-request-id I got the issue where we got the invalid token issue, and then the test after that was fine.
Hey Kyle, I’ve been speaking to support over email and they’ve said that the fix is in progress, so not yet implemented? Or is it a different issue you’re referring to?