For Workflows, when there is an issue and the workflow(s) fail, the initial debugging step is to go to the workflows tab, location the workflow and view the executions. To see the details of the Execution you are interested in, you would go to the Actions Column and choose “Download Execution”
When the file is generated, the filename is set to “<WORKFLOW_NAME><TODAYS_DATE>.csv”. While this is fine if you only need to look at one, it is not helpful if you need to look at multiple executions, which is often the case when there is an issue with the Workflow Engine. In that case, the next one you choose to download will be named “<WORKFLOW_NAME><TODAYS_DATE> (1).csv” and so on, incrementing by the format of the OS for handling duplicate files.
Where thi is not helpful is that there is now no way to link this back to s specific execution without opening it up, reviewing the contents and determining if it matches the log. Similarly, if you download the same execution on different days, the names of the files will be different.
A better naming convention would be:
“<WORKFLOW_NAME>-<EXECUTION_DATE_TIME>-<TODAYS_DATE>.csv”
This would allow someone to easily be able to see which run it was for and the date downloaded for review. It would also allow sorting them by execution then load. You would still run into using the OS duplicate file naming convention if you pull it multiple times in a day, but I think that is reasonable. Adding the time component to today could work too, but the name becomed very long. Being able to see that you downloaded it today may also reduce the need to re-download it again for completed/failed ones that are no longer processing.