If a SAS Enterprise Guide process flow contains an Export As a Step in Process node, subsequent nodes further in the process flow might start running before the Export As a Step in Process node is finished. The SAS Enterprise Guide Export As a Step in Process task does not submit SAS code. Therefore, it executes on a separate thread and is not considered part of the sequential execution of SAS code on the server. This is expected behavior.

Use PROC EXPORT instead of Export As a Step in Process to include the export code submission in the sequential processing on the SAS server.

A workaround is to add a dummy SAS program node and link it to the Export As a Step in Process node. Here is an example of a dummy SAS program node: data _null_; run; 

The link to the dummy SAS program node blocks the flow execution from moving forward until the export step is complete.

Operating System and Release Information

A fix for this issue for SAS Enterprise Guide 8.3 is available at: