Execution logs are kept for 30 days. After that, they are permanently deleted.
Open the logs
You can reach execution logs two ways:- From the Actions page: select View Execution Logs in the header to open a table of all execution logs.
- From a single action: open the action and select the Executions tab, next to Configuration, to see that action’s metrics and its logs only.
Table actions
The Actions column on each row offers View Execution, Copy Link, Download Code, and Quick View.
The Actions column menu on an execution log row.
Download code and debug locally
Use Download Code to save the executed code as a Python file. To download several at once, select multiple rows and use the action bar at the bottom to get a Zip with one Python file per log.
Selected execution log rows with the action bar for downloading a Zip of Python files.
python3 name_of_log_file.py in your terminal to reproduce the action’s exact output. Edit the file and run it again until you get the result you want, then move your changes back into the action.
Quick view
Quick View opens a dialog with the executed code, the timestamp, and high-level metadata.
The Quick View dialog with an execution's code, timestamp, and metadata.
The execution log page
Open a log by selecting its timestamp or View Execution. The page shows all metadata along with the code and context that ran.
An execution log page with its metadata, executed code, and context.

An execution log page with the execution context expanded as formatted JSON.