This is a production-blocking issue affecting our entire Retool setup.
Since recently, localStorage values are no longer being passed into queries. Every query that depends on them is now receiving empty values, causing widespread failures across the app.
There have been no changes on our end, which points to a likely regression from a recent Retool update.
Impact:
Core workflows are broken
Multiple queries failing simultaneously
Entire app ecosystem is effectively down
This needs immediate attention.
Please confirm:
If this is a known issue
If it’s tied to a recent release
Any available workaround or rollback
Happy to share repro steps if needed, but this is urgent and blocking production.
Our retool is also experiencing the same issue, on page load the localstorage containing an auth token which we use for API calls is not working. When we go into edit and run the API queries via “Run & Save” they do work. It seem to be on page load which is causing an issue.
Hi @Ashish_Agarwal , thanks for reaching out! I’m sorry to hear you’re hitting this issue. Please can you come back to me on the following:
Confirm your Retool Cloud domain
Send across a screenshot of how you’re setting localStorage and passing localStorage values into queries
Send a screenshot of localStorage values in the State tab of your browser dev tools (example included in the attached screenshot)
I ran a quick check in my Cloud org and confirmed that setting values in localStorage and passing them into a REST API query is working as expected. That said, this doesn’t rule out the possibility of an issue affecting your org.
I’ve reproduced the behaviour - this affects queries that run on page load (either set to run automatically or “Run on page load” is enabled in the Advanced query settings). It looks like a timing issue with how Retool initialises localStorage relative to when page load queries fire. When queries are triggered manually a moment later, localStorage is ready and the values pass through correctly.
A temporary workaround I’ve found is to use a JS Query set to "Run on page load" that explicitly calls query.trigger() on dependent queries.
I understand this causes significant inconvenience and the workaround is less than ideal. I’m escalating this to our engineering team and will keep you posted with any updates.
My goal: I used {{localStorage.values.token}} for passing token in headers but today it stopped working, now i fixed it temporarily in some apps by returning token from transformer
Issue: why {{localStorage.values.token}} sent as undefined in headers while passing it through transformer works as expected
Steps I've taken to troubleshoot: I just make a transformer out of it and pass token in header through transformer
Additional info: (Cloud or Self-hosted, Screenshots)
