Can I export a log as a step in the project, even if there are errors?

[jtlbg]

I want to save the log of every run of a process. I know I can use EG's "Export Log as a Step In Project" feature, and I know this will even create timestamped files to avoid overwriting a previously output log. All good so far.

However, if an error occurs in the step that generated the log, EG won't proceed to the export step, so it doesn't export the log. Saving the logs is much more important when errors occur so it is unfortunate that I've managed to get this working in the happy path but not the case where it really matters.

It seems like my current solution would work if I could force EG to continue running a branch of a process flow even in the face of errors. Is this possible?

I've read the thread on log saving which discusses proc printto and other workarounds, but I'm keen to find a solution which is simple and a natural use of the tool.

I am using Enterprise Guide 7.13 on SAS 9.4 on Linux.

[Criptic]

If you are using the EG'S Export Log as a Step In Project feature then on the first screen out 4 you can set a checkmark that will export the log even if the programm itself throws an error.

[jtlbg]

@Criptic - that's initially what I thought, but that's not actually what happens. It seems that the export task runs, but it exports a previous version of the log, not the latest one with the errors in it.

[Miracle]

perhaps try this approach as suggested here?

https://communities.sas.com/t5/SAS-Enterprise-Guide/Export-SAS-log-to-external-files/td-p/287838

[jtlbg · Accepted solution]

I'm silly. I found the option I'm looking for. In Project properties you can choose Continue Execution on errors. This lets the Export task run even when the previous step error'd.

[Criptic]

That's exactly the check mark I was talking about