agent loop detected: agent kept repeating the same assign Microsoft 365 lic

Not specified by the original author.

TL;DR

Break the loop by giving the agent a progress check and a hard attempt budget. The agent is repeating the assign Microsoft 365 licenses step because its success test never passes, usually because it checks the wrong signal or the step result never reaches its state. Add a direct verification read from Entra ID, stop after a small number of attempts with a clear escalation, and fix the underlying success test so one success ends the step.

agent loop detected: agent kept repeating the same assign Microsoft 365 licenses step

Use this when

• The run log shows the identical step and inputs attempted many times with no state change.
• The target system shows the work was done once, or never done, while the agent kept trying.
• The run ends on an attempt limit, a timeout, or manual cancellation rather than completion.

Not for this skill when

• The agent retries a few times with backoff and then succeeds. That is healthy retry behaviour, not a loop.
• A human keeps restarting the run manually. Fix the operational process instead of the agent.

Steps

1. Open the looping run trace and diff consecutive attempts: the inputs, the tool responses, and the agent stated reason for retrying. Identify the exact success condition the agent believes is unmet. Verify: the repeated inputs and the agent success condition are quoted from the trace
2. Check Entra ID directly for the step result and compare reality with the agent belief: if the result exists, the agent verification is broken; if it never exists, the create call itself is failing in a way the agent misreads as retryable. Verify: ground truth and the agent belief are contrasted explicitly
3. Fix the verification: replace any indirect signal, such as searching a list page or parsing a chatty response, with a direct read of the created object by its identifier in Entra ID, and treat a confirmed read as step success. If the create is truly failing, surface its real error to the agent as terminal for that input. Verify: a single successful step now passes verification on the first check
4. Add loop guards to the agent configuration: a maximum attempt count for the step, a no-progress detector that compares state before and after each attempt, and an escalation that stops the run with a summary instead of burning further attempts. Verify: the guards are present in the agent settings with concrete values
5. Re-run the scenario for one hire end to end and confirm the assign Microsoft 365 licenses step executes once, verifies, and the run moves on. Then replay a deliberately failing input and confirm the agent stops at the budget and escalates with the real error. Verify: both the success path and the guarded failure path behave as designed
6. Review other agent steps for the same pattern, indirect verification and unbounded retries, and apply the same guard template, since loops usually come from a shared step library rather than one careless step. Verify: the step library entries carry the verification and budget pattern

Why it happens

Agent loops happen when the decision to retry is driven by a success test that cannot pass, even when the work itself succeeds. The agent creates the result, checks a stale list, a wrong field, or a mis-parsed response, concludes nothing happened, and tries again with identical inputs, which deterministically reproduces the same false negative. Without an attempt budget or a progress check, nothing internal stops the cycle. Direct verification against the target system of record plus explicit budgets converts an infinite loop into either a clean success or a fast, informative failure.

Variants and edge cases

Loop creates duplicates each attempt

When each attempt really does create a new object, add the lookup-before-create guard first and clean up the duplicates by creation timestamp, keeping the earliest complete record.

Loop alternates between two steps

Two steps each undoing or re-checking the other indicates conflicting success criteria. Align both steps on one shared state read before adding budgets.

Loop only for one hire record

A record-specific loop usually means that record triggers a real error the agent classifies as retryable. Log the raw target error for that record and fix its data.

Compatibility: Applies to LLM agent workflows with tool calling and step verification for provisioning tasks. Requires agent configuration access.

Provenance

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

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

Thread query: agent loop detected: agent kept repeating the same assign Microsoft 365 licenses step and failed with error

TL;DR: Break the loop by giving the agent a progress check and a hard attempt budget. The agent is repeating the assign Microsoft 365 licenses step because its success test never passes, usually because it checks the wrong signal or the step result never reaches its state. Add a direct verification read from Entra ID, stop after a small number of attempts with a clear escalation, and fix the underlying success test so one success ends the step.

Not specified by the original author.

TL;DR

Stop carrying the whole run in the conversation and move state into tools and storage. The agent overflows because it accumulates every hire record, log, and page it has seen while trying to assign Microsoft 365 licenses. Restructure so each hire is processed in a fresh bounded step, reference data is fetched on demand and summarized, and progress lives in a run store the agent reads back in small pieces.

agent context overflow during assign Microsoft 365 licenses: context limit error

Use this when

• The run fails with a context or token limit error partway through assign Microsoft 365 licenses, later for larger cohorts.
• The agent trace shows long accumulated histories, pasted tables, or full page contents retained across steps.
• Short single-hire runs of the same workflow succeed reliably.

Not for this skill when

• A single hire with one huge source document overflows alone. Split that document handling instead of the whole run design.
• The error is a provider outage mislabelled as a limit. Check provider status before redesigning.

Steps

1. Measure the growth: from the run trace, estimate how much context each hire adds, including tool outputs the agent keeps, and identify the bulkiest contributors such as full directory listings, verbose API responses, or screenshots described in text. Verify: the top context contributors per hire are named with rough sizes
2. Externalize run state: write per-hire status, identifiers, and decisions to a run store such as a table or file the workflow owns, and have the agent read back only the current hire slice instead of remembering the cohort. Verify: the agent completes a hire using only the stored slice plus its instructions
3. Process hires in bounded units: one hire, or a small fixed batch, per agent invocation with a fresh context, orchestrated by a simple loop outside the model that tracks overall progress and handles retries. Verify: a multi-hire test run completes with flat per-invocation context use
4. Shrink tool outputs at the source: request only needed fields from lookups, summarize long lists with counts and the relevant rows, and store large artefacts as references the agent opens only when a decision truly needs them. Verify: sample tool outputs are visibly smaller with no decision-relevant loss
5. Resume the failed cohort with the new structure and confirm the run completes assign Microsoft 365 licenses for every hire, then check output quality on the last hires equals the first, since quiet degradation is the overflow failure mode that does not crash. Verify: first and last hire results pass the same spot checks
6. Set a cohort sizing rule in the runbook from the measured per-hire cost, with headroom, and add a context-use warning in run reporting before the hard limit so growth is caught as a trend. Verify: the sizing rule and the warning both exist

Why it happens

Agent context is a finite working memory, and provisioning runs are naturally unbounded: every hire, lookup, and verification adds text the agent keeps carrying. Designs that let the conversation itself be the database guarantee overflow at some cohort size, usually mid-run on the busiest hiring day. The model does not need to remember the cohort; it needs the current hire, the rules, and a reliable place to put results. External state, bounded invocations, and lean tool outputs are the standard architecture for long agent work, and they also improve consistency because each hire gets the agent full attention.

Variants and edge cases

Reference data is the bulk, not hires

Load catalogues such as app or license lists as searchable tool data the agent queries per decision instead of pasting them into context.

History needed for audit, not for decisions

Keep the full trace in run logs outside the model context; the agent needs conclusions, not its own transcript.

Overflow at the verification step

Verification that re-reads everything the run produced doubles the load. Verify from the target system state per hire at completion time instead.

Compatibility: Applies to LLM agent provisioning workflows processing cohorts of hires. Requires workflow orchestration and run storage access.

Provenance

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

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

Thread query: agent context overflow during assign Microsoft 365 licenses: context limit error failed the run

TL;DR: Stop carrying the whole run in the conversation and move state into tools and storage. The agent overflows because it accumulates every hire record, log, and page it has seen while trying to assign Microsoft 365 licenses. Restructure so each hire is processed in a fresh bounded step, reference data is fetched on demand and summarized, and progress lives in a run store the agent reads back in small pieces.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: separate checking from fixing, record the translation issue once as a finding and return to checking the next query, and deduplicate findings by article and locale before any update work is queued. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Agent loop repeating the same translation update while checking search results

Use this when

• Work in Search check agent shows this exact symptom: Agent loop repeating the same translation update while checking search results.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: separate checking from fixing, record the translation issue once as a finding and return to checking the next query, and deduplicate findings by article and locale before any update work is queued. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Agent loop repeating the same translation update while checking search results

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - agent stuck loop detected repeating the same translation update while trying to check help center search results for an error query error failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

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

Why it happens

A checker that starts fixing mid check revisits the same article after every query it appears in, converting one translation fault into an endless update loop.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_BtKJ9jw-Jk2-F748Xc2lTw

Resolved from the public thread: https://vectle.com/posts/pst_BtKJ9jw-Jk2-F748Xc2lTw

Thread query: agent stuck loop detected repeating the same translation update while trying to check help center search results for an error query error failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: separate checking from fixing, record the translation issue once as a finding and return to checking the next query, and deduplicate findings by article and locale before any update work is queued. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.