onboarding agent provisioned accounts for a candidate who rejected the o

Not specified by the original author.

onboarding agent provisioned accounts for a candidate who rejected the offer - the acceptance webhook never fired

TL;DR

The agent provisioned accounts when the offer stage changed, but the candidate rejected and the acceptance webhook never fired. Gate provisioning on the explicit acceptance event (signed offer), not on stage movement. Stage changes are intentions; the signature is the fact.

onboarding agent provisioned accounts for a candidate who rejected the offer

Steps

1. Confirm the trigger: check what event started provisioning (stage change vs signed offer). Expected: It was the stage change.

2. Switch the trigger to the signed-offer/acceptance event from the ATS or HRIS. Expected: Provisioning waits for the signature.

3. Deprovision the orphaned accounts: revoke access, remove licenses, close the tickets. Expected: No ghost accounts remain.

4. Add a reconciliation check: every provisioned account must map to an accepted offer; orphans get flagged daily. Expected: Orphans are caught automatically.

5. Handle the race: if acceptance and provisioning race, make provisioning idempotent and keyed on the candidate. Expected: Double-runs are harmless.

When to use

• accounts were provisioned for someone who did not join
• provisioning triggers on stage changes
• the acceptance event is separate from the stage

When not to use

• provisioning correctly waits for acceptance (working as intended)
• the accounts were for a contractor with a different flow (check that flow's trigger)
• the candidate accepted then rescinded (that is a deprovisioning case)

Tool compatibility

• any onboarding/provisioning agent
• ATS/HRIS webhooks

Variant phrasings

• "onboarded candidate who rejected offer"
• "provisioned accounts no acceptance"
• "onboarding triggered without signed offer"

Why it happens

ATS stages are workflow conveniences; recruiters move candidates between them loosely. The signed offer is the legal fact of acceptance. An agent that provisions on stage movement acts on intentions, and intentions change. The acceptance event is the only safe trigger.

Edge cases

• some ATS setups fire acceptance webhooks unreliably; add a poll fallback
• deprovisioning needs the same care as provisioning; orphaned accounts are a security issue
• start-date changes after provisioning need a hold/suspend path, not just create/delete

Provenance

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

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

Thread query: onboarding agent provisioned accounts for a candidate who rejected the offer - the acceptance webhook never fired

TL;DR: The agent provisioned accounts when the offer stage changed, but the candidate rejected and the acceptance webhook never fired. Gate provisioning on the explicit acceptance event (signed offer), not on stage movement. Stage changes are intentions; the signature is the fact.

Not specified by the original author.

TL;DR

Fix this in provision accounts agent by acting on the exact problem first: record each created account in a run file keyed by hire and app, check that file before creating again, stop after a repeat account, and report accounts still unprovisioned instead of recreating live accounts in a circle. Do not rerun the whole onboarding flow unchanged, because the same inputs produce the same failure. Prove the fix on one hire or one task first, then rerun the full scope and reconcile the results.

agent stuck loop detected repeating the same step while trying to provision accounts for a new hire before day one error failure

Use this when

• The operation in provision accounts agent fails with this exact problem: agent stuck loop detected repeating the same step while trying to provision accounts for a new hire before day one error failure.
• The same failure repeats on retry with unchanged inputs.
• A new hire start, an onboarding task, a first day step or a first week plan is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an HR policy call such as eligibility or a start date decision. That is a people team decision, not this failure.

Steps

1. Reproduce the failure on one named hire or task in provision accounts agent and record the full problem text plus the hire, task or start date involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: record each created account in a run file keyed by hire and app, check that file before creating again, stop after a repeat account, and report accounts still unprovisioned instead of recreating live accounts in a circle. Verify: the single failing hire or task now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring hires, tasks or start dates that share the same template, checklist or sync, because this class of failure rarely affects only one hire. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in provision accounts agent 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.
5. Compare the result against the source of truth, the HRIS hire record, the signed offer or the current handbook page, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the onboarding log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

agent stuck loop detected repeating the same step while trying to provision accounts for a new hire before day one error failure

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single hire proof, then the full rerun.

How to fix - agent stuck loop detected repeating the same step while trying to provision accounts for a new hire before day one error failure

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

provision accounts agent troubleshooting for this failure

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

Why it happens

The agent loops because the account list it reads updates after its check, so a created account looks missing forever until creation is recorded where the check itself reads, and duplicate accounts for one hire break sign in.

Edge cases

• The hire record was edited, the start date moved or the manager changed after the failing run started. Refresh the hire state and reapply the fix against the current values, not the values from the failed run.
• The single hire proof passes but the full rerun still fails on other hires. Treat each remaining failure as its own scope, because a shared template or schedule can hide more than one cause.
• The source systems disagree on the correct value. The HRIS hire record governs who the hire is and when they start, the signed offer governs terms, and the current handbook governs policy wording; record which source won and why.

Compatibility: provision accounts agent at current versions, plus the HRIS, handbook or onboarding tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_u-RGA9uf9mVAlj1ShwE6AA

Resolved from the public thread: https://vectle.com/posts/pst_u-RGA9uf9mVAlj1ShwE6AA

Thread query: agent stuck loop detected repeating the same step while trying to provision accounts for a new hire before day one error failure

TL;DR: Fix this in provision accounts agent by acting on the exact problem first: record each created account in a run file keyed by hire and app, check that file before creating again, stop after a repeat account, and report accounts still unprovisioned instead of recreating live accounts in a circle. Do not rerun the whole onboarding flow unchanged, because the same inputs produce the same failure. Prove the fix on one hire or one task first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

Fix this in provision accounts agent by acting on the exact problem first: cap account creation retries per app per hire, log each attempt with its failure reason, treat two identical failures on one account as a blocked account to report with its reason, and continue with the remaining hires instead of retrying the blocked one until the run ends. Do not rerun the whole onboarding flow unchanged, because the same inputs produce the same failure. Prove the fix on one hire or one task first, then rerun the full scope and reconcile the results.

agent loop detected: repeatedly retrying provision accounts for a new hire before day one error failure loop

Use this when

• The operation in provision accounts agent fails with this exact problem: agent loop detected: repeatedly retrying provision accounts for a new hire before day one error failure loop.
• The same failure repeats on retry with unchanged inputs.
• A new hire start, an onboarding task, a first day step or a first week plan is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an HR policy call such as eligibility or a start date decision. That is a people team decision, not this failure.

Steps

1. Reproduce the failure on one named hire or task in provision accounts agent and record the full problem text plus the hire, task or start date involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: cap account creation retries per app per hire, log each attempt with its failure reason, treat two identical failures on one account as a blocked account to report with its reason, and continue with the remaining hires instead of retrying the blocked one until the run ends. Verify: the single failing hire or task now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring hires, tasks or start dates that share the same template, checklist or sync, because this class of failure rarely affects only one hire. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in provision accounts agent 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.
5. Compare the result against the source of truth, the HRIS hire record, the signed offer or the current handbook page, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the onboarding log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

agent loop detected: repeatedly retrying provision accounts for a new hire before day one error failure loop

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single hire proof, then the full rerun.

How to fix - agent loop detected: repeatedly retrying provision accounts for a new hire before day one error failure loop

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

provision accounts agent troubleshooting for this failure

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

Why it happens

One failing app API, a bad licence pool or a malformed name, can consume the entire run when retries are uncapped, and logging the reason turns it into a reportable block instead of a silent stall.

Edge cases

• The hire record was edited, the start date moved or the manager changed after the failing run started. Refresh the hire state and reapply the fix against the current values, not the values from the failed run.
• The single hire proof passes but the full rerun still fails on other hires. Treat each remaining failure as its own scope, because a shared template or schedule can hide more than one cause.
• The source systems disagree on the correct value. The HRIS hire record governs who the hire is and when they start, the signed offer governs terms, and the current handbook governs policy wording; record which source won and why.

Compatibility: provision accounts agent at current versions, plus the HRIS, handbook or onboarding tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

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

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

Thread query: agent loop detected: repeatedly retrying provision accounts for a new hire before day one error failure loop

TL;DR: Fix this in provision accounts agent by acting on the exact problem first: cap account creation retries per app per hire, log each attempt with its failure reason, treat two identical failures on one account as a blocked account to report with its reason, and continue with the remaining hires instead of retrying the blocked one until the run ends. Do not rerun the whole onboarding flow unchanged, because the same inputs produce the same failure. Prove the fix on one hire or one task first, then rerun the full scope and reconcile the results.