Scheduled Purge issues

#Purge isn't deleting files

• Nothing old enough yet. Purge only removes files older than the configured age — check modified times against your cutoff (months/years use calendar-aware math, so “1 month” isn't always 30 days).
• Pattern doesn't match. A run reporting “no files” matched nothing. Test with * to confirm the target has the files you expect, then narrow (mind case, e.g. *.CSV vs *.csv).
• Permissions. Remote targets need list and delete rights — re-test the credential.
• Root target rejected. FileAgent refuses to purge a bare drive, share, bucket, or container — point at a folder inside the location.

#Deleted more or fewer files than expected

Open the purge run in Logs first — the detail records what was scanned, deleted, and skipped, the fastest way to see exactly what the rule matched.

• Too many? The pattern was broader than intended (the default * matches everything) or the age threshold was larger than you meant.
• Too few? The pattern was too narrow (wrong extension or case) or the files simply weren't old enough.
• Confirm the target path. Make sure the job points at the folder/prefix you intended, not a parent or sibling.

#Recovering purged files

Going forward, validate a purge with a narrow pattern and a manual run before scheduling it, and keep archive or backup behavior in place for anything you might need back. See Scheduled Purge.