I am seeing some jobs end like this - there is definitely not a manual intervention by someone to stop the job:

1/6/2010 11:40:07 AM Debug Task (6587) was added to processlist: Read file
1/6/2010 11:40:07 AM Info Task started: Read file
1/6/2010 11:40:07 AM Info Task completed: Read file
1/6/2010 11:40:07 AM Debug Setting previous task in TaskProcessCompleted: Read file
(21a7f050-0a51-4f9b-9cce-0e3fd64b69f5) in job: File Delivery
1/6/2010 11:40:07 AM Debug Process status - About to SendTaskProcess (6587)
1/6/2010 11:40:07 AM Debug Process status - About to RemoveTaskProcess (6587)
1/6/2010 11:40:07 AM Debug Task (6587) was removed from processlist: Read File
1/6/2010 11:40:07 AM Info Job process was aborted by user.
1/6/2010 11:40:07 AM Debug Job (2573) was removed from processlist: File Delivery
1/6/2010 11:40:07 AM Debug Next execution (2) for job 'File Delivery' is: 1/6/2010 2:40:00 PM
1/6/2010 11:40:07 AM Info Job completed: File Delivery

The purpose of the "read file" task, is to confirm that the file was successfully copied to the destination; if not, it is supposed to fail and send an alert. In this case, it did not fail, but does the "aborted by user" message mean that it is possible that file that was to be read was not present at the destination, without actually causing the job to fail?

(This is important, because we are using the read task as a verification of a successful file delivery; and would like to know if there is a way to verify, based on the information in the log that the file was successfully read; or whether it may not have been successfully read, without actually triggering a task failure.)