Can a file transfer job have an error, but still complete successfully?
Yes. If a job has a non-fatal error, processing continues through all steps of the job.
What are some examples of non-fatal errors?
- Problem deleting one or more temporary files
- Error executing a pre-processing command, but “Continue after pre-processing error” is checked on the transaction (only occurs in Enterprise Edition)
- Problem creating one or more advanced troubleshooting files
- Error zipping archive files
- Error closing a file being transferred
- Error deleting an uploaded file after a problem during transmission
- Decryption or verification key is not valid for current date
- Unable to determine the size of an uploaded or downloaded file
- ASCII file size not within tolerance
What non-fatal errors result in an overall job status of Warning?
A status of Warning is used for jobs that had at least one non-fatal error that might have affected the integrity of the file(s) being transferred, which include the following:
- Error closing a file being transferred
- Error deleting an uploaded file after a problem during transmission
- Decryption or verification key is not valid for current date
- ASCII file size not within tolerance
What action should I take for jobs with a status of Warning?
As soon as possible, check the destination file to ensure that no file corruption has occurred. If the destination file is corrupt or you are uncertain of its integrity, delete the destination file and rerun the file transfer job. If the source file is no longer available from the original location and you have an archive of the source file, rerun the job using the archived copy of the source file.