
Last Friday I fixed a bug in one of our server side functions where it became clear that not all records where considered because of pagination. I see the value of pagination when sending data to the client via a REST interface (or something like that), but when I query data on the server it feels kinda wired. In this cases I wanted to get all foreign keys from a certain field of that collection. So I needed to recursively cursor over the whole thing. Is there a way to avoid this?
We use Web/ JS on the client and Node.js in the Functions.

Hi, what is the current size you are working with in pagination?

Default, which is 25. But the problem is always there.

If it's the cloud you can change the limit up to 100 and in the latest version up to 5000
To do so send Query.limit(100)
with your request.

But it's recommend you use the pagination for performance and overwhelming your sever.
Recommended threads
- Function deployments stuck on waiting
Project ID: **orteos** Function ID: ** crawl_worker** Deployment ID: ** 68a8a8cc668c72293b33** Theres multiple deployments waiting in line
- Urgent: Functions randomly failing with ...
Hi all, I’m facing a critical issue with my Appwrite self-hosted instance where some of my functions have randomly started failing with the following error: `I...
- Synchronous function execution timed out...
Hello everyone! I know this is an old question that many of you have already asked, but I'm doing it again because I can't understand the real solution or impl...
