From 105776eab3baab4a26bee7223fac7a5b936039c0 Mon Sep 17 00:00:00 2001
From: bjoaquinc <75667013+bjoaquinc@users.noreply.github.com>
Date: Fri, 6 Dec 2024 15:43:52 -0500
Subject: [PATCH] docs: add note about awaiting `useLazyFetch` (#30171)

---
 docs/3.api/2.composables/use-lazy-fetch.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/3.api/2.composables/use-lazy-fetch.md b/docs/3.api/2.composables/use-lazy-fetch.md
index b84e54b407..9e861800be 100644
--- a/docs/3.api/2.composables/use-lazy-fetch.md
+++ b/docs/3.api/2.composables/use-lazy-fetch.md
@@ -16,6 +16,10 @@ By default, [`useFetch`](/docs/api/composables/use-fetch) blocks navigation unti
 `useLazyFetch` has the same signature as [`useFetch`](/docs/api/composables/use-fetch).
 ::
 
+::note
+Awaiting `useLazyFetch` in this mode only ensures the call is initialized. On client-side navigation, data may not be immediately available, and you should make sure to handle the pending state in your app.
+::
+
 :read-more{to="/docs/api/composables/use-fetch"}
 
 ## Example