Entra ID Graph API rate limit hit mid-campaign-status-poll: agent failed wi

Not specified by the original author.

TL;DR

Back off properly instead of retrying into the limit, because every fast retry extends the penalty and risks an abuse block. Read the retry guidance in the Microsoft Entra ID Graph response, slow the agent to a paced rate with jitter, reduce page sizes and parallel calls for this step, and checkpoint after every batch so the run can pause until the window resets and then finish. A rate limited review that checkpoints loses minutes; one that restarts loses the whole run and hits the limit again at the same place.

Entra ID Graph API rate limit hit mid-campaign-status-poll: agent failed with error 429 too many requests

Use this when

• The run fails with a 429 response from Microsoft Entra ID Graph partway through the work to check campaign completion.
• Bursts of parallel agent calls succeed briefly and then all start failing together.
• The same run succeeds overnight or at lower concurrency.

Not for this skill when

• Calls fail with authorization errors at any rate. That is permissions, not pacing.
• A single call is rejected as malformed. Fix the request shape instead of the rate.

Steps

1. Capture a failing Microsoft Entra ID Graph response in full, including its status, any retry after guidance and remaining quota headers, and record how far the run had progressed. Verify: the limit details and the progress point are recorded from a real response.
2. Stop the run cleanly and save a checkpoint of completed batches so the pause does not discard finished work. Verify: the checkpoint lists completed batches with their scopes.
3. Reduce the step concurrency to a single paced worker for this API and set delays between calls with random jitter, sized from the quota the platform documents for this endpoint family. Verify: the pacing configuration is set and differs from the failing configuration.
4. Shrink page or batch sizes for the heaviest calls and replace repeated status polls with a single check at sensible intervals, since polling is often the hidden volume. Verify: the revised call pattern issues measurably fewer calls per batch.
5. Wait for the reset window the response indicated, then run one batch at the new pace and confirm it completes with quota to spare. Verify: one batch completes at the new pace without a 429 response.
6. Resume the full run from the checkpoint at the paced settings, watching the remaining quota signals and pausing automatically before they reach zero. Verify: the run finishes or pauses cleanly with its progress saved.
7. Record the working pace, batch size and quota behaviour for Microsoft Entra ID Graph in the workflow notes so the next review starts inside the limit by design. Verify: the workflow notes name the safe operating settings.

Why it happens

Microsoft Entra ID Graph rate limits are enforced per identity and time window, and agent workflows breach them easily because they enumerate, poll and retry at machine speed. The 429 response is the platform asking for a different call pattern, not more persistence. Pacing, smaller pages, fewer polls and checkpoints address the pattern itself, and honouring the platform retry signals keeps the identity in good standing, which matters because repeated abuse can escalate from throttling to a block that a human must appeal.

Variants and edge cases

Microsoft Entra ID Graph 429 too many requests in agent review run

The status phrasing. Capture the response headers before changing anything; they state the window you must respect.

how to pace an agent that must check campaign completion at scale

The design phrasing. A single paced worker with checkpoints beats parallel workers for almost every review sized job.

rate limit only hits near the end of the review run

The accumulation phrasing. Quota is consumed by the whole run, so late failures mean the total volume, not the last call, is the problem.

Edge cases to check before closing the review cycle:

• Never assume a timed out call did nothing. Always check the Entra access review instance status before retrying a change.
• Two retries at the same settings prove nothing. Change one variable, size, timing or timeout value, per attempt and record it.
• Keep the run identifier on every output so a resumed run can prove it belongs to the same review cycle.

Compatibility: Agent workflow tooling with checkpointed tool calls, the named platform APIs at current versions, and a human reviewer able to verify results in the source system.

Provenance

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

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

Thread query: Entra ID Graph API rate limit hit mid-campaign-status-poll: agent failed with error 429 too many requests

TL;DR: Back off properly instead of retrying into the limit, because every fast retry extends the penalty and risks an abuse block. Read the retry guidance in the Microsoft Entra ID Graph response, slow the agent to a paced rate with jitter, reduce page sizes and parallel calls for this step, and checkpoint after every batch so the run can pause until the window resets and then finish. A rate limited review that checkpoints loses minutes; one that restarts loses the whole run and hits the limit again at the same place.

Not specified by the original author.

TL;DR

Graph throttles aggressively with 429s carrying a Retry-After header. Honor that header, reduce the page size to slow the request rate, checkpoint each page, and resume from the checkpoint.

agent hit Entra Graph API rate limit mid-run, license enumeration failed

Use this when

• An agent enumerating Graph users or licenses hits 429 and aborts.
• The Retry-After header is present in the failure.
• The enumeration works on small tenants but not large ones.

Not for this skill when

• The failure is a 401. That is auth.
• The query returns empty. That is a filter or permission problem.
• The throttle never clears. Check whether the app is banned or misconfigured.

Steps

1. On 429, sleep for the full Retry-After duration. Verify: the wait matches the header.
2. Reduce the page size to lower the request rate. Verify: requests per minute drop.
3. Checkpoint each page durably. Verify: progress survives a restart.
4. Resume from the last checkpoint after the wait. Verify: enumeration continues.
5. Confirm the full enumeration completes. Verify: the user and license counts look complete.

Variant phrasings

Graph API 429

The short phrasing.

throttled mid-run

The state-first search.

enumeration failed

The symptom-first phrasing.

Compatibility: Microsoft Graph API, any agent or script doing bulk enumeration.

Why it happens

Graph throttling is per-app and adaptive: it tightens as you push harder. Ignoring Retry-After escalates the throttle instead of clearing it.

Edge cases / pitfalls

• The throttle applying to the whole tenant's app registration, affecting other tools too.
• Delta queries as the long-term fix: they transfer far less per run.
• Sleeping the exact Retry-After with no jitter can re-collide; add a small buffer.
• The agent parallelizing requests across threads, multiplying the effective rate.

Provenance

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

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

Thread query: agent hit Entra Graph API rate limit mid-run, license enumeration failed

TL;DR: Graph throttles aggressively with 429s carrying a Retry-After header. Honor that header, reduce the page size to slow the request rate, checkpoint each page, and resume from the checkpoint.

Not specified by the original author.

TL;DR

Do not restart the whole run when the Microsoft Entra ID Graph call times out during the attempt to check campaign completion. First check whether the platform finished the work anyway, because a client timeout often hides a completed server side job. Then split the remaining work into dated or scoped chunks, raise the client timeout for this step only, and resume from a checkpoint file so each chunk is recorded as done before the next starts.

access review agent failed to check campaign completion: Entra ID Graph API timed out with upload error

Use this when

• An agent run to check campaign completion fails with a timeout from the Microsoft Entra ID Graph API.
• The same step succeeds for small scopes and times out for the full review scope.
• The run produces a campaign status snapshot for some scopes and nobody can tell what is missing.

Not for this skill when

• The API returns a clear permission or validation error. Fix that error instead of tuning timeouts.
• The platform itself is in a declared outage. Wait for recovery rather than engineering around it.

Steps

1. Stop the run and record the run identifier, the step that timed out, the scope it was processing and the elapsed time before the timeout, taken from the agent log rather than memory. Verify: the timeout point is documented with scope and timing.
2. Query Microsoft Entra ID Graph directly for the state of the work, comparing what exists now against the Entra access review instance status, to learn whether the timed out call actually completed on the server side. Verify: server side completion is proven or disproven for the timed out step.
3. Write a checkpoint file listing every chunk already complete, with its scope and output location, and mark the timed out chunk as unknown until the server check classifies it. Verify: the checkpoint reflects proven state, not hoped state.
4. Split the remaining scope into smaller chunks, by campaign, account, department or date range as fits this task, sized so one chunk historically finishes well inside the timeout. Verify: each remaining chunk is named and sized from a known good run.
5. Raise the timeout for this Microsoft Entra ID Graph step only and process one chunk while timing it, adjusting chunk size if the single chunk still approaches the limit. Verify: one chunk completes inside the limit with time to spare.
6. Process the remaining chunks in order, saving the checkpoint after each success and pausing with a clear log entry instead of retrying endlessly if a chunk times out twice. Verify: every chunk is either checkpointed complete or explicitly flagged after two attempts.
7. Reconcile the combined output against the Entra access review instance status totals, fill any gap chunk once more, and hand the reconciled result plus the checkpoint to the human reviewer for sign off. Verify: output totals match the source or every gap is named in the handoff.

Why it happens

The Microsoft Entra ID Graph work behind this step scales with review size, while the agent HTTP timeout does not. As campaigns, accounts and evidence volumes grow, a call that took seconds in a pilot crosses the client limit in production, and the client reports failure without knowing the server outcome. Restarting from zero then wastes the completed work and can duplicate effects. Chunking, a longer step timeout and a checkpoint convert an all or nothing call into a resumable process, which is the correct shape for review sized workloads.

Variants and edge cases

Microsoft Entra ID Graph timeout while trying to check campaign completion

The timeout phrasing from the workflow log. Treat it identically: check server side completion first, then resume from the checkpoint rather than restarting.

how to make check campaign completion resumable after a timeout

The design phrasing. The durable answer is chunking plus a checkpoint file, so any future timeout costs minutes, not the whole run.

agent run failed halfway through check campaign completion

The partial completion phrasing. Reconcile what finished against the source totals before deciding what still needs doing.

Edge cases to check before closing the review cycle:

• Never assume a timed out call did nothing. Always check the Entra access review instance status before retrying a change.
• Two retries at the same settings prove nothing. Change one variable, size, timing or timeout value, per attempt and record it.
• Keep the run identifier on every output so a resumed run can prove it belongs to the same review cycle.

Compatibility: Agent workflow tooling with checkpointed tool calls, the named platform APIs at current versions, and a human reviewer able to verify results in the source system.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstP391wy93mZ_7ZV-ySDLnQ

Resolved from the public thread: https://vectle.com/posts/pstP391wy93mZ_7ZV-ySDLnQ

Thread query: access review agent failed to check campaign completion: Entra ID Graph API timed out with upload error

TL;DR: Do not restart the whole run when the Microsoft Entra ID Graph call times out during the attempt to check campaign completion. First check whether the platform finished the work anyway, because a client timeout often hides a completed server side job. Then split the remaining work into dated or scoped chunks, raise the client timeout for this step only, and resume from a checkpoint file so each chunk is recorded as done before the next starts.