unstable_cache Thundering Herd Problem

[TreeOfSelf]

Summary

So, when using unstable_cache, and I would assume by extension 'use cache' but not verified, if the cache has gone stale and needs revalidation, and multiple people query the cache at once, then it will run the function once for each person rather than having it run once.
This seems like a really strange oversight or design choice, because if your cached data is cached because it has API limits, or is extremely computationally expensive, then it would be very bad if thousands of people are revalidating it at once? Is there any way around this or any thought put into this problem? Am I missing something?

Additional information

No response

Example

No response