Query class pagination limit behavior change in Appwrite v0.13

Determine whether requesting a limit higher than the server‑enforced maximum triggers an error or is silently capped when using the Query class in Appwrite SDK versions 0.12.x versus 0.13.x.

The documentation states that limit() controls result set size and that the server enforces a maximum to avoid resource exhaustion, but it does not specify whether exceeding that limit returns a validation error or returns a truncated set with the maximum allowed count. Additionally, the behavior may differ between self‑hosted and Cloud deployments.

Does the API return a 400 Bad Request (or similar) when limit > server max in v0.13? Does the response still include a total count of matching documents? Is there a recommended migration pattern for handling limit‑related errors when upgrading SDK versions?