diff --git a/docs/resources/control-flow/backend-logic/backend-query/query-collection.md b/docs/resources/control-flow/backend-logic/backend-query/query-collection.md
index 1c8d1285..37db013e 100644
--- a/docs/resources/control-flow/backend-logic/backend-query/query-collection.md
+++ b/docs/resources/control-flow/backend-logic/backend-query/query-collection.md
@@ -80,6 +80,16 @@ The instructions to query a Supabase table are almost the same, except that for
     </iframe>
 </div>
 
+:::warning[Limitations of Supabase Streaming with Filters]
+When using Supabase query with real-time updates enabled, you have the following limitations:
+
+- **Only One Filter is Supported:** Supabase streaming supports only a single filter. Combining multiple filters (e.g., `isActive = true AND city = 'Los Angeles'`) is not allowed.
+- **Delete Events are not Filterable:** Streaming queries do not detect deletions, even if the deleted row matches the filter condition. For example, If you are streaming rows with the filter `city = 'New York’` and a row is deleted, the query output will not reflect the deletion.
+- **Updates that remove Rows from Filters are not Tracked:** Changes that make a row no longer match the filter condition (e.g., updating `isActive` from `true` to `false`) will not trigger an update in the query output.
+
+For more details, refer to the limitations mentioned in the [**official Supabase docs**](https://supabase.com/docs/guides/realtime/postgres-changes?queryGroups=language&language=js&queryGroups=database-method&database-method=dashboard#delete-events-are-not-filterable).
+:::
+
 ## Using Query Data
 
 The documents retrieved from the backend query can be used to set the record values to the widgets