# Token used before issued problem! (Time sync?!)

**URL:** <https://community.auth0.com/t/token-used-before-issued-problem-time-sync/62472>\
**Category:** Get Help\
**Tags:** jwt, api, access-token, auth0, login\
**Created:** [May 9, 2021, 5:49pm UTC](https://community.auth0.com/t/token-used-before-issued-problem-time-sync/62472 "2021-05-09T17:49:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [May 11, 2021, 9:08pm UTC](https://community.auth0.com/t/token-used-before-issued-problem-time-sync/62472/3 "2021-05-11T21:08:51Z")

</div>

Hi @gutisAlex,

This could be a clock skew issue.

Take a look at this thread about a similar issue. You can use the `leeway` param to give some room for clock variance.

> [@AccessToken is not (yet) valid](https://community.auth0.com/t/accesstoken-is-not-yet-valid/59002/3):
>
> Hi @info40, Sounds like a clock skew issue. You can add some leeway to your expiration time. Are you using the auth0 SPA sdk in your front end? If so, you can send a leeway param with your request. Here is the doc for it: [https://auth0.github.io/auth0-spa-js/interfaces/auth0clientoptions.html#leeway](https://auth0.github.io/auth0-spa-js/interfaces/auth0clientoptions.html#leeway)

---

_[View the full topic](https://community.auth0.com/t/token-used-before-issued-problem-time-sync/62472)._