evidence collector error pagination broken only first page of users collect

Not specified by the original author.

TL;DR

Fix this in the evidence collector user pull by doing this first: follow the next-page cursor in the source API until it returns empty, log the page count and total users per run, and alert when the total changes sharply between runs. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

pagination broken with only first page of users collected

Use this when

• The operation fails with this exact problem: pagination broken with only first page of users collected.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the evidence collector user pull, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: follow the next-page cursor in the source API until it returns empty, log the page count and total users per run, and alert when the total changes sharply between runs. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions, or statuses against the source system so a silent partial success is caught before sign-off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
6. Record the fix, the triggering input, and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied, and the evidence of success.

Why it happens

The collector read the first page and treated it as the full list because the pagination cursor in the response was ignored, so most users were never collected.

Variant phrasings

evidence collector error pagination broken only first page of users collected failure

The verbatim form searchers paste from the console or ticket. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix this failure in practice

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting the symptom-first form

The phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Vanta, Drata, and Secureframe class compliance platforms at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/psttLMivyJsjJX8Dhfaz6nGA

Resolved from the public thread: https://vectle.com/posts/psttLMivyJsjJX8Dhfaz6nGA

Thread query: evidence collector error pagination broken only first page of users collected failure

TL;DR: Fix this in the evidence collector user pull by doing this first: follow the next-page cursor in the source API until it returns empty, log the page count and total users per run, and alert when the total changes sharply between runs. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in evidence collector pagination by acting on the exact problem first: fix the collector to follow the pagination link in each Microsoft Graph response until no further page is returned, rerun the user collection, and reconcile the collected count against the total user count shown in Entra ID. Do not rerun the whole job or collection unchanged, because the same inputs produce the same failure. Prove the fix on one control, account or batch first, then rerun the full scope and reconcile the counts.

Entra ID users beyond first 999 never collected

Use this when

• The operation in evidence collector pagination fails with this exact message or symptom: Entra ID users beyond first 999 never collected.
• The same failure repeats on retry with unchanged inputs.
• An audit, evidence package or compliance review is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an auditor judgment or a control design choice. That is a review discussion, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in evidence collector pagination, and copy the full message plus the control, account or item involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: fix the collector to follow the pagination link in each Microsoft Graph response until no further page is returned, rerun the user collection, and reconcile the collected count against the total user count shown in Entra ID. Verify: the smallest failing scope now completes, or the named control, account or item behaves as the fix predicts.
3. Check the neighbouring controls, accounts or items that share the same connection, mapping or owner, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in evidence collector pagination on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in evidence collector pagination so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Graph style APIs return one page at a time, and a collector that reads only the first response collects exactly one page of users no matter how large the tenant is.

Variant phrasings

Entra ID users beyond first 999 never collected

The verbatim form searchers paste from the console, ticket or audit request. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - evidence collector pagination error Entra ID users beyond first 999 never collected

The how to phrasing for the same failure in evidence collector pagination. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

evidence collector pagination troubleshooting for this failure

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If evidence was already sent to an auditor in the wrong state, correct the record with a dated note explaining what changed, rather than silently replacing files in the package.
• If two settings or mappings could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: evidence collector pagination at current versions, plus the admin console or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_O0k5xJWcXWNAkEC8yUGRaQ

Resolved from the public thread: https://vectle.com/posts/pst_O0k5xJWcXWNAkEC8yUGRaQ

Thread query: evidence collector pagination error Entra ID users beyond first 999 never collected

TL;DR: Fix this in evidence collector pagination by acting on the exact problem first: fix the collector to follow the pagination link in each Microsoft Graph response until no further page is returned, rerun the user collection, and reconcile the collected count against the total user count shown in Entra ID. Do not rerun the whole job or collection unchanged, because the same inputs produce the same failure. Prove the fix on one control, account or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the agent working set for compliance evidence by doing this first: page the compliance evidence material in small batches, keep a running index of item references and one-line summaries outside the context, and load full records only for the batch being worked on. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

context overflow while loading compliance evidence data in one context

Use this when

• The operation fails with this exact problem: context overflow while loading compliance evidence data in one context.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the agent working set for compliance evidence, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: page the compliance evidence material in small batches, keep a running index of item references and one-line summaries outside the context, and load full records only for the batch being worked on. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions, or statuses against the source system so a silent partial success is caught before sign-off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
6. Record the fix, the triggering input, and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied, and the evidence of success.

Why it happens

The job loads the entire history or attachment set at once, exceeds the context window, and loses the thread of the work instead of processing it in verifiable batches.

Variant phrasings

context window limit error agent couldn't fit compliance evidence data in context failure

The verbatim form searchers paste from the console or ticket. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix this failure in practice

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting the symptom-first form

The phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Vanta, Drata, and Secureframe class compliance platforms at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_FnC3XFGPjkY5KrwtWfUiFg

Resolved from the public thread: https://vectle.com/posts/pst_FnC3XFGPjkY5KrwtWfUiFg

Thread query: context window limit error agent couldn't fit compliance evidence data in context failure

TL;DR: Fix this in the agent working set for compliance evidence by doing this first: page the compliance evidence material in small batches, keep a running index of item references and one-line summaries outside the context, and load full records only for the batch being worked on. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.