From e1ee888e2f245ae78c59e6c186ef3fd069eeaac2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9s=20Aguiar?= Date: Wed, 11 Sep 2024 06:41:19 -0700 Subject: [PATCH] fix: remove inaccurate note in ReadChanges (#835) --- docs/content/interacting/read-tuple-changes.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/content/interacting/read-tuple-changes.mdx b/docs/content/interacting/read-tuple-changes.mdx index d85f083de..822fc6c1e 100644 --- a/docs/content/interacting/read-tuple-changes.mdx +++ b/docs/content/interacting/read-tuple-changes.mdx @@ -169,7 +169,6 @@ Once there are no more changes to retrieve, the API will return the same token a :::note - The default page size is 50. The maximum page size allowed is 100. -- The API response will not return all the changes immediately. There will be a delay of one minute between the time that you add or delete a tuple and the time that you see it in the Read Changes API response. - The API response does not expand the tuples. If you wrote a tuple that includes a userset, like `{"user": "group:abc#member", "relation": "owner": "doc:budget"}`, the Read Changes API will return that exact tuple. :::