From 38fa10611acb3bb37cd34e4b18a2c7cf362ed05c Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Mon, 8 Jun 2026 13:15:12 +0000
Subject: [PATCH] docs: clarify scan_history page_size default and unsampled
 behavior

---
 models/track/public-api-guide.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/models/track/public-api-guide.mdx b/models/track/public-api-guide.mdx
index 2022c24c5b..6c11362af6 100644
--- a/models/track/public-api-guide.mdx
+++ b/models/track/public-api-guide.mdx
@@ -471,7 +471,7 @@ losses = [row["loss"] for row in history]
 
 ### Get paginated data from history
 
-If metrics are being fetched slowly on our backend or API requests are timing out, you can try lowering the page size in `scan_history` so that individual requests don't time out. The default page size is 500, so you can experiment with different sizes to see what works best:
+`scan_history` returns the complete, unsampled history for a run (unlike `run.history()`, which returns a sampled view). If metrics are being fetched slowly on our backend or API requests are timing out, you can try lowering the page size in `scan_history` so that individual requests don't time out. The `page_size` parameter controls how many history records are fetched per API request (default: `1000`). It is independent of the `keys` parameter, which filters which metrics are returned. You can experiment with different sizes to see what works best:
 
 ```python
 import wandb