(ESI) Token expiry too far in the future

Recently I’ve been getting errors that token expiry is too far in the future. I examined the tokens using JWT.io and it confirmed that the tokens themselves have the expiry that is too far in the future. My code pulls the expiry directly from the token. Has anyone else encountered this issue? If so what have you done to work around it? I’ve done some searching but haven’t found anyone else encountering this issue.

Basically; in my application whenever an ESI call fails it pings my discord so I’m aware of it, had it not been doing this I’m sure I wouldn’t have caught it. The API call does fail, it returns a 403.

Thanks in advanced!

Thank you! I didn’t actually think to look there haha.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.