I haver written a code node, in EG3, that generates a bunch of reports based on a meta data table. Each report gets some data processing followed by a proc tabulate statement.
After running the node the log opens and the node gets a red cross and border. There are no error or warning messages in the log. Could it be that the length of the log triggers this? The log is 149612 lines long.
When EG3 submits a job to SAS, it "listens" for events from the SAS server that indicate an error. Occasionally SAS triggers an error event that doesn't correspond to an error in the resulting SAS log.
In this case, I think you can consider the error indication as erroneous -- or at least not important for your output. EG 4.1 fixes this by actually examining the SAS log for error lines and displaying the dreaded "red X" only when the log actually contains an error.
With EG4 you can completely mask errors by using PROC PRINTO and direct the log to a file. I find this effective when I check for and correct errors in a stored process and do not want the big red X in EG. You can also trigger the big red X by printing the string ERROR: to the log