route_access_denied

[Ashley B.15]

Hi,

Would someone be able to help with the following error

401 route_access_denied.

I've encountered the above a couple of times now and would like some advice on best to handle it?

We use refresh tokens to obtain new access tokens, which appears to be working fine (did encounter and issue with tokens previously - tokens being truncated) but this has now been resolved.

We cache the tokens and obtain new tokens when they are due to expire.

What should we do when we encounter this error?

Thanks in advance

[awb]

@Greg-DB we have encountered the above again. Any more news your end? Is there anyway to escalate it. Thanks again for all your help.

[Greg-DB]

@awb This is still open with the relevant engineering team. I'll check in with them.

[aryehsanders]

This appears to be a more widespread issue - Maestral users have been reporting route_access_denied errors as well: https://github.com/samschott/maestral/issues/1065

[Greg-DB]

Thanks for the note! The team is currently working on this. I'll follow up here once we have news on that.

[Greg-DB]

That team has deployed a fix to address this. Please let us know if you're still see any more instances of this now. (If so, please share samples of the 'X-Dropbox-Request-Id' response header values.) Thanks!

[aryehsanders]

Thanks!