This is a blast from the past - this thread from 2015. Solved: Oddball Error with Copy Files Task - SAS Support Communities I'm on SAS EG 8.2 Update 5 (8.2.5.1277)  I've been converted a number of our projects (and creating from new) from using PC Files Server to using EG Copy File Task, coupled with proc import/export Unix to Unix and then  Copy Files task to return the .xlsx to Windows.  We have had a few password/access issues and a couple of other things that PCFS has evolved into doing that are clumsy, which I want to avoid. I also see Copy Files Task as a stepping stone away from PCFS or SAS Base (Windows) as our organisation moves to Viya on cloud.  I too love the flexibility Copy Files Task offers and usually set it up with macro vars for input_path, file_name and target_path, in a parameters file so I can comment the heck out of it. I get the same problem as in 2015.  Sometimes (quite often) the code node following the CFT starts to run before the CFT has finished.  The job I normally run next is to delete the file from Unix which the CFT is moving. It gives the same as in 2015: the log just shows the "resolving macro expressions" and does not complete the transfer.   Unlike the 2015 post, I already have this a predecessor linked to the next code node, so the 2015 solution does not work for me. I had thought of putting the next code node to sleep (data _null_; call sleep(15,1); run;) to try and hold it back.  Given @ChrisHemedinger  reply in 2015 about this being (possibly) related to timing and the CFT task using a background thread, which the subsequent job, finishing quicker then terminates the CFT, I am hopeful this may work. Nope, perhaps related more to the time it starts.  When I run it a second time, from the Export code node, it works fine.  In both cases, it looks like the Delete Excel Unix code is waiting (in yellow).  So this does seem to be a first time thing.  When I hit this on another project, I broke the flow after the CFT, but that is a bit clunky. This seems to me like it fails the first attempt, then I struggle to make it fail again. I thought it was just me!  Anyone else having this same kind of issue and did you find a away past it?  If sleeping in the next step doesn't work (which it just didn't), then I feel my only option left is to remove the delete temp unix file bit from that flow (perhaps give it a flow all of it's own).  Or perhaps I should throw in a few code boundaries quit; run; at the end of the export.  Not found a way, yet... ... View more