Cache not invalidating

💬 Queries and Resources
1

I'm trying to invalidate the cache of a query before running it again. However, after I invalidate the cache, the query still runs from cache...

Here is the code I am running to invalidate the cache:

await getHSCompanyContacts.invalidateCache();
await getHSCompanyContacts.trigger();

Here is a screenshot of what happens:

Screenshot 2025-02-05 at 12.31.12 PM
Screenshot 2025-02-05 at 12.31.12 PM1037×198 23.1 KB

3

Hey @Nick_Michniok! This is a known issue for mobile apps, but should work as expected otherwise. Is this a mobile or web app?

4

@Darren, it's a web app.

5

Hi @Darren, any update on this? It's still happening quite often. I've had to remove all cacheing of all queries in the mean time. My SQL query does have a retool variable referenced inside of it in the WHERE clause. Might this be impacting it?

Thanks
Nick

6

Thanks for confirming that. I haven't been able to reproduce the issue in my local testing, but there's a variety of factors that could be at play. For context, each query result is cached individually based on its unique combination of parameters, but they should still all be invalidated at the same time. :thinking:

Are you able to provide a JSON export of your app so that I can see how it's constructed in more detail?

image
image1300×252 31.1 KB

7

Yes, I can get you that, where should I send it? Also, where does the cache live?
Thanks
Nick

8

You can DM me here or send an email to darren@retool.com. :+1:

All cached query results are saved in a Redis database on the Retool backend.