An advanced task does not register a file error using the [FileErrorCode] macro when the file is sent to multiple destinations. The file error code macro is reported as 0 (no error) when there was an error for one of the destinations. Why is its value zero in this situation?

This is due to the behavior of the [FileErrorCode] macro. The value of this macro is reevaluated every time the file is sent to a new destination. So, if the file fails to send to the first destination but succeeds when sent to the next destination, the file error code will be set to zero. 

It was determined that the Progress Product is functioning as designed. An enhancement request has been submitted as an Idea on the Progress Community. To promote the Idea, click on this link: https://moveit.ideas.aha.io/ideas/MOVEIT-I-1244. Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea. Its priority will be evaluated as customer demand weighs in through Article Feedback and through vote count in the Ideas Portal.

For detailed information on how to submit an Idea, please refer to Knowledge Base article How to submit an enhancement request for a Progress product?.

If possible, use a traditional task instead. The source can be configured to delete files after transfer, which will only occur if the file was successfully uploaded to all destinations. Alternatively, custom scripts can be used to create an error counter for an advanced task. For more details on this setup contact MOVEit tech support.