.. _2026-11-11-sign-in-token-reliability_release:

=================================================================================
2026-11-11 - Sign-In Checks Allow for Clock Drift and Retry Key Fetches
=================================================================================

Release
==================
AgileData.io - A Little Leeway: More Forgiving Sign-In Checks

Every request to AgileData carries a sign-in token that is checked before any work is done. Very occasionally, a request was rejected with "Invalid Auth Token", and the logs didn't say why.

**What was happening:**

* The reason for a rejection was never recorded, so one-off failures couldn't be explained
* The most likely causes were a small clock difference, which can make a fresh token look "used too early", and a brief failure fetching the keys used to check tokens
* Neither case allowed any leeway or a retry

Token checks now allow a few seconds of clock difference and retry the key fetch once. When a token is rejected, the reason is now logged, so any remaining issues can be found quickly.

**What this means for you:**

* The two most likely causes of one-off "Invalid Auth Token" errors are now handled
* Faster diagnosis if a sign-in problem does occur

Last Refreshed
===========================
*Doc Refreshed: 2026-11-14*