{"_id":"57d864992e393e2d0068deb0","__v":0,"initVersion":{"_id":"55faf11ba62ba1170021a9aa","version":"1.0"},"user":{"_id":"5613e4f8fdd08f2b00437620","username":"","name":"Emile Young"},"project":"55faf11ba62ba1170021a9a7","createdAt":"2016-09-13T20:42:01.563Z","changelog":[],"body":"You can save and view **all task logs** produced during a task. These logs include the explicit commands used to execute your task (cmd.log) and details of the execution, including input and output data, metadata and resources used (job.json).  The Platform saves these logs by default for tasks initiated via the visual interface or via the API. \n\nWhile you can view these logs via the Platform's visual interface, you have to opt in to viewing these logs via the API. To do so, use the **save logs** option under **Hints** when you describe a tool or workflow on the Platform, and set the value to the file type you'd like to save and report as a log file.\n\nYou can also use the **save logs** hint to tell the Platform which file types you consider as logs in addition to the logs collected by default. These files will be saved and viewable as logs on the Platform.\n\n\nThe **save logs** feature is especially helpful for users of the API, who can use logs to better understand how their data is processed and help optimize their executions. For instance, one of our Seven Bridges team members recently used this feature to understand how file size affected the processing speed of two different algorithms. Learn how to use the **save logs** setting in the [documentation](doc:advanced-features-of-the-tool-editor#section-configure-the-log-files-for-your-tool).","slug":"did-you-know","title":"Did you know: Save and view all task logs"}

Did you know: Save and view all task logs


You can save and view **all task logs** produced during a task. These logs include the explicit commands used to execute your task (cmd.log) and details of the execution, including input and output data, metadata and resources used (job.json). The Platform saves these logs by default for tasks initiated via the visual interface or via the API. While you can view these logs via the Platform's visual interface, you have to opt in to viewing these logs via the API. To do so, use the **save logs** option under **Hints** when you describe a tool or workflow on the Platform, and set the value to the file type you'd like to save and report as a log file. You can also use the **save logs** hint to tell the Platform which file types you consider as logs in addition to the logs collected by default. These files will be saved and viewable as logs on the Platform. The **save logs** feature is especially helpful for users of the API, who can use logs to better understand how their data is processed and help optimize their executions. For instance, one of our Seven Bridges team members recently used this feature to understand how file size affected the processing speed of two different algorithms. Learn how to use the **save logs** setting in the [documentation](doc:advanced-features-of-the-tool-editor#section-configure-the-log-files-for-your-tool).