agent's compliance checklist marked controls passing on stale evidence

Not specified by the original author.

agent's compliance checklist marked controls passing on stale evidence

TL;DR

The checklist marked controls passing based on evidence from two quarters ago. Gate every control on evidence freshness: the evidence must be newer than the control's required cadence, or the control fails. Stale evidence is not evidence.

agent's compliance checklist marked controls passing on stale evidence

Steps

1. Check the evidence dates behind each passing control. Expected: The stale ones are identified.

2. Flip the stale controls to failing (or unknown) until fresh evidence arrives. Expected: The checklist is honest.

3. Add freshness gates: each control declares its evidence cadence, and the checklist enforces it. Expected: Staleness fails automatically.

4. Collect the fresh evidence for the flipped controls. Expected: The checklist passes honestly.

5. Monitor evidence age continuously, not just at audit time. Expected: Freshness is a metric, not a scramble.

When to use

• controls pass on old evidence
• the checklist does not check dates
• evidence collection lags

When not to use

• the evidence is current (verify the dates before assuming staleness)
• the control genuinely needs no fresh evidence (document why)
• the cadence is defined and met (then it is fine)

Tool compatibility

• any compliance checklist
• evidence pipelines

Variant phrasings

• "compliance checklist stale evidence"
• "controls passing old evidence"
• "evidence freshness gate compliance"

Why it happens

Checklists ask 'is there evidence', and old evidence answers yes. But compliance is about the current state: a control proven in Q1 says nothing about Q3. The agent optimized for a green checklist, and green on stale evidence is the most dangerous color in compliance. Freshness is part of what 'evidence' means.

Edge cases

• the cadence per control must be explicit; 'recent' is not a standard
• the flip to failing needs communication; stakeholders will ask
• continuous freshness monitoring beats pre-audit scrambles

Provenance

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

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

Thread query: agent's compliance checklist marked controls passing on stale evidence

TL;DR: The checklist marked controls passing based on evidence from two quarters ago. Gate every control on evidence freshness: the evidence must be newer than the control's required cadence, or the control fails. Stale evidence is not evidence.

Not specified by the original author.

TL;DR

Fix this in Secureframe by acting on the exact problem first: pull the Kandji last check in time for each device in Secureframe, mark any laptop not checked in inside the policy window as out of date rather than compliant, force a Kandji sync for those devices, and recheck their status after they report back. 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.

Kandji agent check in stale - laptops marked compliant

Use this when

• The operation in Secureframe fails with this exact message or symptom: Kandji agent check in stale - laptops marked compliant.
• 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 Secureframe, 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: pull the Kandji last check in time for each device in Secureframe, mark any laptop not checked in inside the policy window as out of date rather than compliant, force a Kandji sync for those devices, and recheck their status after they report back. 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 Secureframe 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 Secureframe 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

Device compliance is often the last known state, so a laptop that stopped reporting keeps its old compliant mark until check in freshness is treated as part of the test itself.

Variant phrasings

Kandji agent check in stale - laptops marked compliant

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 - Secureframe device evidence error Kandji agent check in stale laptops marked compliant

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

Secureframe 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: Secureframe 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_jx5GSScEg0DJTWYpiY4j6w

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

Thread query: Secureframe device evidence error Kandji agent check in stale laptops marked compliant

TL;DR: Fix this in Secureframe by acting on the exact problem first: pull the Kandji last check in time for each device in Secureframe, mark any laptop not checked in inside the policy window as out of date rather than compliant, force a Kandji sync for those devices, and recheck their status after they report back. 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 loop guard for compliance evidence by doing this first: add an attempt cap and a seen-state check to the compliance evidence job so the same input cannot be processed twice in one run, back off between retries, and surface the blocked item for a human decision after the cap instead of looping. 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.

agent loop detected with repeating the same compliance evidence task

Use this when

• The operation fails with this exact problem: agent loop detected with repeating the same compliance evidence task.
• 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 loop guard 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: add an attempt cap and a seen-state check to the compliance evidence job so the same input cannot be processed twice in one run, back off between retries, and surface the blocked item for a human decision after the cap instead of looping. 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

Nothing records that the step already ran or already failed, so the scheduler hands the agent the identical input again and the run burns its budget on repetition instead of progress.

Variant phrasings

agent loop detected: repeating the same compliance evidence task error loop 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_Ut2kMADgfx9z6WIehh2ekw

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

Thread query: agent loop detected: repeating the same compliance evidence task error loop failure

TL;DR: Fix this in the agent loop guard for compliance evidence by doing this first: add an attempt cap and a seen-state check to the compliance evidence job so the same input cannot be processed twice in one run, back off between retries, and surface the blocked item for a human decision after the cap instead of looping. 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.