Logging

Once your workflow execution has completed, either successfully or with a failure, you will be able to view logs detailing the execution process. Links to logs are provided in response to the job status request mentioned above and can be viewed in the browser. Note, it can sometimes take up to 30 seconds for the logs to be generated and returned by this endpoint, so please try again if the links are initially missing.

Logs require authentication and authorization to view and only the user who initially requested the workflow execution can view the associated logs. Logging details can also be returned directly in a call to the job status endpoint under the "message" key, although the separate logs will include more details about the workflow execution.

A number of log files are produced when a workflow completes, these include:

• node_stage_in.log – logs from the STAGEIN step of the workflow, these can be useful if your inputs to the workflow are incorrect or not accessible to the WR
• node_stage_out.log – logs from the STAGEOUT step of the workflow, these are useful when your workflow failed to generate the expected STAC files or they were generated incorrectly
• <step>.log files – these are generated for each step in your CWL workflow and contain the stdout from the step execution code, helping you to determine errors within the steps of your workflow