Sounds like it could be the internal resourcechecker tasks that get triggered because of too little available disk space on your server. Check in logs/service/current/fmecleanup.log for critical messages.
To modify the thresholds, look in fmeServerConfig.txt under the "Cleanup Watch" headings, specifically:
- CLEANUP_WARN_MINDISKSIZE_GB
- CLEANUP_WARN_MINDISKSIZE_PCT
- CLEANUP_CRITICAL_MINDISKSIZE_GB
- CLEANUP_CRITICAL_MINDISKSIZE_PCT
You can also set notification topics that you can configure to e.g. send you an email if the available disk space gets below the WARN or CRITICAL levels, very handy.
I ran into this issue also; our server was deleting job lists and I hadn't changed anything. @david_r was right; I was finally able to log into the machine hosting FME Server (we have an AWS environment and I hadn't needed access to the machine itself before this), and the C: drive was almost full! As it turns out, my predecessor had set up a workspace to export a backup file every day and had it stored on the C: drive, and we had over a year's worth of backup files stored there. They were being written into C:/ProgramData, which doesn't show up in the file explorer unless you type it into the address bar specifically, so I couldn't even see where all this data was without really digging for it. Anyway, I made some changes and it seems to be working better now. Lesson learned: pay attention to where your backups are going.
This thread set me on the right path to solving the issue, so thank you!
