Have you seen caching behave incorrectly with async await?

When multiple views request the same resource concurrently using async/await directly on the API layer, each caller triggers its own fetch, leading to duplicate network requests, increased battery usage, and doubled traffic. The solution is a shared async task cache that deduplicates in-flight requests so only one fetch fires regardless of how many callers are waiting.