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.
If you're looking for the ability to easily save an output log post-execution, and don't need to do it in an automated fashion, you can right click any line of the "Results - Messages" tab and choose "Save as".
This will prompt you to save a Text file, which you can name whatever you want. You could then easily load this text file into a database or store it in a useful location.
If you are looking for a more automated logging process, my initial post still applies.
Are you leveraging the Alteryx Scheduler/Command Line execution, or using another method via VBScript?
If you are using the existing Command Line execution you can write the log to a file by simply including a ">File.log" after the workflow name/configuration.
If you're using another method, the best option would probably be the User Settings in your Designer, which would allow you to define a Logging Directory.
The downside to this option is that it will happen for ALL workflows, including ones that you are testing.
Once you have the logs saved, you can easily read them in as part of a process or load them to a database.
The final option if you want to configure this for each workflow (this would still require some more effort to finalize), is to use a Workflow Event after execution to email the log to yourself. Then you could leverage outlook rules to save this somewhere. The advantage of this option is that it can be configured per workflow.