The dynamic token doesn’t seem to be cleared when clicking clear cache.
I fetched a fresh token manually and pasted into the Static Token field and it connects.
The dynamic token I enabled and was working yesterday shows an authentication error.
Also the static token doesn’t wrap in the textfield. It stretches the whole page out.
I have a 1hr dynamic token. When and how does BF handle the token refresh?
And this too on the frontend
Warning : Undefined variable $token in \bricksforge\includes\external-api-loops\ExternalApiLoops.php** on line676
Hey 
I’ve identified and fixed the issue you reported. The “Clear Cache” button was previously only clearing API response cache but not the stored dynamic tokens. This has now been resolved.
What’s been fixed:
The “Clear Cache” button now properly clears both API cache AND stored dynamic tokens
This will force Bricksforge to fetch a fresh token on the next request
Answers to your questions:
Dynamic Token Refresh: Bricksforge handles token refresh reactively - it only refreshes your 1-hour token when it receives a 401 authentication error from the API. It doesn’t proactively refresh before expiration, which explains why your token worked yesterday but shows auth errors today (the token expired but hadn’t been refreshed yet).
Static Token UI Issue: The text field stretching issue is noted and will be addressed in a future UI update.
The fix ensures that when users click “Clear Cache”, it now properly resets the token authentication state, forcing Bricksforge to fetch fresh tokens on the next API request. The fix will be deployed in the next update
You rock!
It kept giving the 401 error and it doesn’t seem to be fetching the token.
I have it on a local dev right now, but I’ll upload it accessible online probably within 2 weeks if you still want to take a look later.