# `useFetch` with `watch: false` and reactive key, `getCachedData` gives the old, first initialized key
Multiple `useLazyAsyncData` within a composable becomes non lazy
good first issuebug🔨 p3-minor
`useFetch` stale key with `watch: false` and `execute()` (manual mode)
pending triagepossible regression
Using `getCachedData` together with `await useLazyAsyncData` causing it to not be pending anymore
pending triageneeds reproduction
3.17.2 and 3.17.3 broke the "lazy" of useLazyAsyncData
pending triagepossible regression
When using useAsyncData with the same key, the status does not change between page navigations.
pending triagepossible regression
useAsyncData doesn't block navigation with lazy: false
3.xpending triage