Since the upgrade it appears that most files are deleting automatically however there are files that do not. Could someone let me know why some jobs will not delete automatically? I cannot seem to figure out what stops some jobs from deleting. Is there any criteria that would prevent a job from deleting after the 24-25 hour time period? It seems that some jobs never delete. I have left them on for days to see if they would but they havent and I do not understand why.
Successfully completed jobs (i.e., jobs that complete the workflow and reach a terminal state such as paused, processed, etc.) are automatically deleted from the system every 24 hours. Failed jobs are retained in the system 'indefintely,' until they are manually deleted via Job Manager > Delete (single or all jobs).
I am not sure what is going on then because I have a few pages of files that have not deleted. Please see below. I checked the date and time on the server and it is May 9th @ 9:26 am. The snip below is the last page of the completed jobs queue. I have three more pages of this and they are all from May 7th. The May 8th files seem to be deleting fine. Any suggestions as to why these particuler files would not be deleting?
There is no reason (other than a SW upgrade) that I am aware of that would lead to your described FFCore job deletion behavior. Xerox customer service should be able to debug the problem if it persists.
Option 1. Recover Windows 10 Automatically Deleted Files by Restoring the Previous Version
Option 2. Run the System File Checker to Restore Automatically Missing Files
System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files.
1. Open an elevated command prompt
2. Type the following command, and then press Enter:
DISM.exe /Online /Cleanup-image /Restorehealth
3. At the command prompt, type the following command, and then press ENTER: sfc /scannow
4. After the process is finished, you may receive one of the following messages:
• Windows Resource Protection did not find any integrity violations.