I have seen this in MAX Hot Folders were there is an issue with the .csv
IE: I had someone edit a system generated CSV and accidently changed 1 of the header names, when processed the .csv was moved to Recovery Folder.
The files that wind up in the Recovery folder should be the result of a system failure during processing (e.g., computer hang).
What causes a hot folder process to place a file in the recovery folder? I see no errors in the Job properties that would indicate an error, but sometimes, the file is in the recovery folder instead of the folder directed by the save node. Job properties say the last atttempted preset is the save node.