I actually have no idea what's going on now.. Seeing this pop up in my emails prompted me to check my function invocations and now I'm seeing database queries behind use cache: remote executing on every function invocation, whereas they weren't when I made the original thread you've linked.

This might even explain why my usage costs have skyrocketed since switching to fluid too 😕

Ui, yeah that is exactly what I was afraid of for my usage, as the calculations that I do are quite expensive, financial data crunching of many transactions. So if there is no caching of that data, I would burn through cpu time very quickly.

Good thing you got notified 🙂

I know that "use cache" is not deemed stable yet, so maybe the quick fix way would be to revert to unstable_cache, but i really like the "use cache" way of doing things...

I just tried reverting my usage back to "use cache" - nothing changed

Reverted to unstable_cache - now back to seeing "Using cache | Data Cache" in my function invocations and requests being cached are missing from the invocation logs.

I really don't understand why one works and the other doesn't, considering both are available in Next stable. Even more confused by the response from staff in my previous thread since it seems to be completely wrong.

Last I tried with unstable_cache, doing keys like post:${postId} was rather sketchy and invalidating it rarely worked properly, so for that I'm just using Upstash.

Really hope they get "use cache" sorted soon since the DX is way better.

Thank you for trying the migration to unstable_cache. I am right with you when it comes to the DX. I was on the verge of migrating to vercel for the hosting, but that is currently a blocker for me and I will probably hold out until "use cache" is working correctly.

Hopefully vercel can jump into this thread to clear things up and help us out ;)