GraphQL error: CustomerAccessTokenRenew access denied

We’re starting to experience a critical bug with our customerAccessToken renewal logic. It looks like the customerAccessTokenRenew mutation is running into permission issues. There’s nothing in the documentation that implies special permissions required for this mutation.

Any help would be greatly appreciated @swalkinshaw. It’s only a matter of time before this starts to affect our customers, since their access tokens are bound to expire soon.

[swalkinshaw]

Thanks for bringing this up though. Two improvements will likely come from it:

• better description for this mutation
• better error messages instead of just “access denied”

[nickdandakis]

Ah gotcha. Seems a little weird to have a renewal mutation that only works with valid tokens. We’re going to refactor our code to create a new token if expired, and never renew.

Thanks for the prompt replies!