# Network request is sent even with the same `key` for `useFetch`
`useFetch` makes duplicate requests on client-side page navigation when wrapped in a composable
pending triageneeds reproduction
There is a problem with the auto-generated key of useFetch ()
3.xpending triage
`useFetch` is not preserving state when key or url is same
3.xpending triage
With multiple identical calls to a custom useFetch wrapper, query parameter updates are not applied to manual refresh/execute calls
pending triagepossible regression
When I use the method from composable twice, it works weird
3.xpending triage