@@ -161,28 +161,18 @@ See [Application Errors](/functions/error-handling/application-errors.mdx).
161161
162162To ensure uptime and guarantee performance, Convex will catch queries and
163163mutations that try to read or write too much data. These limits are enforced at
164- the level of a single query or mutation function execution. The limits are:
165-
166- Queries and mutations error out when:
167-
168- - More than 16384 documents are scanned
169- - More than 8MiB worth of data is scanned
170- - More than 4096 queries calls to ` db.get ` or ` db.query ` are made
171- - The function spends more than 1 second executing JavaScript
172-
173- In addition, mutations error out when:
174-
175- - More than 8192 documents are written
176- - More than 8MiB worth of data is written
164+ the level of a single query or mutation function execution. The exact limits are
165+ listed in [ Limits] ( /production/state/limits.mdx#transactions ) .
177166
178167Documents are "scanned" by the database to figure out which documents should be
179168returned from ` db.query ` . So for example ` db.query("table").take(5).collect() `
180169will only need to scan 5 documents, but ` db.query("table").filter(...).first() `
181170might scan up to as many documents as there are in ` "table" ` , to find the first
182171one that matches the given filter.
183172
184- Number of calls to ` db.get ` and ` db.query ` has a limit to prevent a single query
185- from subscribing to too many index ranges.
173+ The number of calls to ` db.get ` and ` db.query ` has a limit to prevent a single
174+ query from subscribing to too many index ranges, or a mutation from reading from
175+ too many ranges that could cause conflicts.
186176
187177In general, if you're running into these limits frequently, we recommend
188178[ indexing your queries] ( /database/reading-data/indexes/indexes.md ) to reduce the
0 commit comments