agent bulk deprovision missed shared drives: data left behind

Not specified by the original author.

TL;DR

The offboarding scope was too broad and caught the manager's access. Scope every action to the departing user's identity, preview the change set as a diff, and require approval before applying.

The query

agent's offboarding run removed the manager's shared-drive access: scope error

Use this when

• offboarding removed someone else's access
• the scope included shared resources
• managers report lost access after a report's exit

Not for

• granting access to new hires
• shared-drive permission design
• manual offboarding mistakes

Steps

1. Restore the manager's access immediately and confirm it works. Expected output: the manager is unblocked.
2. Find the scoping bug: the query or filter that included the wrong identity. Expected output: the over-broad selector is identified.
3. Rewrite the scope to match only the departing user's unique ID across all systems. Expected output: the selector returns exactly one user.
4. Add a pre-apply diff showing every permission change, and require approval. Expected output: a human sees the blast radius first.
5. Re-run the verification pass to confirm only the intended access was removed. Expected output: a clean per-system attestation.

Applies to

Offboarding automation, Active Directory, Google Workspace, file share permissions.

Variant phrasings

Scope bug from group expansion

Expand groups to members first, then filter to the departing user.

Shared drive owned by the departing user

Transfer ownership explicitly instead of removing access blindly.

Why it happens

Offboarding queries like 'everyone in this group' or 'all access on this drive' easily include the wrong people. Scoping by unique user ID is the fix.

Edge cases

• Managers often share access with reports; the diff makes that visible.
• Test offboarding in staging with a realistic org chart.
• Keep the approved diff as the audit record.

Provenance

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

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

Thread query: agent's offboarding run removed the manager's shared-drive access: scope error

TL;DR: The offboarding scope was too broad and caught the manager's access. Scope every action to the departing user's identity, preview the change set as a diff, and require approval before applying.

Not specified by the original author.

TL;DR

Fix this in DSR inventory agent by acting on the exact problem first: correct the request record to show that system as not searched, create a manual task for it assigned to its owner, and require a search log or export as evidence before any system can be marked searched in future. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

agent hallucinated system inventory - claimed SaaS tool searched that has no connector

Use this when

• The operation in DSR inventory agent fails with this exact message or symptom: agent hallucinated system inventory - claimed SaaS tool searched that has no connector.
• The same failure repeats on retry with unchanged inputs.
• A privacy request, export, deletion or deadline 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 a legal interpretation or a policy choice. That is a privacy team decision, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in DSR inventory agent, and copy the full message plus the request, system or record 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: correct the request record to show that system as not searched, create a manual task for it assigned to its owner, and require a search log or export as evidence before any system can be marked searched in future. Verify: the smallest failing scope now completes, or the named request, system or record behaves as the fix predicts.
3. Check the neighbouring requests, systems or records that share the same connector, 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 DSR inventory agent 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 DSR inventory agent so a silent partial success is caught before the request is closed. 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 request so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

An agent completing an inventory from the data map alone marks planned coverage as actual coverage, hiding a system that still holds the requester data untouched.

Variant phrasings

agent hallucinated system inventory - claimed SaaS tool searched that has no connector

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

How to fix - agent hallucinated system inventory claimed SaaS tool searched that has no connector

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

DSR inventory agent 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 system, treat that system as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If personal data was already sent to the wrong place or a notice was already sent early, record the incident for privacy assessment first, then apply the fix, and note the affected request in the run record.
• If a legal hold or a verification question is in play, pause deletion or delivery for that request only, resolve the hold or verification, and keep other requests moving.

Compatibility: DSR inventory agent 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_RS8rgTHgxdJxiLcW1bnQZA

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

Thread query: agent hallucinated system inventory claimed SaaS tool searched that has no connector

TL;DR: Fix this in DSR inventory agent by acting on the exact problem first: correct the request record to show that system as not searched, create a manual task for it assigned to its owner, and require a search log or export as evidence before any system can be marked searched in future. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in deletion agent by acting on the exact problem first: break the loop, run the legal hold check before any further deletion attempt and record its result on the request, and only retry the connector once the hold status is known and the original failure cause is fixed. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

loop detected - retrying failed deletion connector without checking legal hold first

Use this when

• The operation in deletion agent fails with this exact message or symptom: loop detected - retrying failed deletion connector without checking legal hold first.
• The same failure repeats on retry with unchanged inputs.
• A privacy request, export, deletion or deadline 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 a legal interpretation or a policy choice. That is a privacy team decision, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in deletion agent, and copy the full message plus the request, system or record 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: break the loop, run the legal hold check before any further deletion attempt and record its result on the request, and only retry the connector once the hold status is known and the original failure cause is fixed. Verify: the smallest failing scope now completes, or the named request, system or record behaves as the fix predicts.
3. Check the neighbouring requests, systems or records that share the same connector, 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 deletion agent 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 deletion agent so a silent partial success is caught before the request is closed. 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 request so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Retrying a deletion that is blocked by a hold or a permission will never succeed, and each retry risks acting on a request that should have been paused on purpose.

Variant phrasings

loop detected - retrying failed deletion connector without checking legal hold first

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

How to fix - agent loop detected retrying failed deletion connector without checking legal hold first

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

deletion agent 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 system, treat that system as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If personal data was already sent to the wrong place or a notice was already sent early, record the incident for privacy assessment first, then apply the fix, and note the affected request in the run record.
• If a legal hold or a verification question is in play, pause deletion or delivery for that request only, resolve the hold or verification, and keep other requests moving.

Compatibility: deletion agent 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__BHKN7en6tx81QodDVWVxQ

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

Thread query: agent loop detected retrying failed deletion connector without checking legal hold first

TL;DR: Fix this in deletion agent by acting on the exact problem first: break the loop, run the legal hold check before any further deletion attempt and record its result on the request, and only retry the connector once the hold status is known and the original failure cause is fixed. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.