This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
For the Output records, any temporary files generated may not be available. The best practice is to set a specific output file for any data or result you would like saved using an Output or Render tool.
Something to consider: copy the tools that write output in the production model and replace the directory path to "%temp%". This is a shortcut that will reference your temporary folder and output the same thing for your review. Take note that temporary files are ....temporary and the duration of their existence is limited. This will not be a perpetual log solution., but it's an easy way to have immediate spot checking available.
The temporary file path will be the folder specified in the System Settings mentioned above plus a GUID-like random string:
@CharlieS To clarify...The Engine Logging feature you describe would provide the same data that is found in the Server Scheduler->Results tab: WF name, Date/Time Created, Date/Time Completed, Execution time, results, etc..?
Currently C/P'ing this info and manually inputting into a file to get an understanding of our scheduled workflows. Would love something more automated...