diff --git a/docs/3.api/3.utils/define-nuxt-component.md b/docs/3.api/3.utils/define-nuxt-component.md
index 7ee1073121..a7b11e07a7 100644
--- a/docs/3.api/3.utils/define-nuxt-component.md
+++ b/docs/3.api/3.utils/define-nuxt-component.md
@@ -36,6 +36,10 @@ export default defineNuxtComponent({
 </script>
 ```
 
+::warning
+Data from `useAsyncData` is only set once in the `setup` hook of your component. This means `refreshNuxtData` will not work with `asyncData`. If you need to re-run `useAsyncData`, you can change it with a `method` of the Option API.
+::
+
 ## `head()`
 
 If you choose not to use `setup()` in your app, you can use the `head()` method within your component definition:
diff --git a/docs/3.api/3.utils/refresh-nuxt-data.md b/docs/3.api/3.utils/refresh-nuxt-data.md
index 89770397b4..5c38f8858f 100644
--- a/docs/3.api/3.utils/refresh-nuxt-data.md
+++ b/docs/3.api/3.utils/refresh-nuxt-data.md
@@ -12,6 +12,10 @@ links:
 `refreshNuxtData` re-fetches all data from the server and updates the page as well as invalidates the cache of [`useAsyncData`](/docs/api/composables/use-async-data) , `useLazyAsyncData`, [`useFetch`](/docs/api/composables/use-fetch) and `useLazyFetch`.
 ::
 
+::warning
+`refreshNuxtData` only works with composition API. `asyncData` hook from the Options API does not work with `refreshNuxtData`.
+::
+
 ## Type
 
 ```ts