Order Run Logs¶
The Order Run Logs show a list of timestamps, nodes, and messages for the processing of a recipe variation.
Order Run Logs aggregate Automation system logs and the logging information from each tool in the toolchain. These logs are available for every order run.
View order run logs¶
- In Automation, select your kitchen.
- Select Orders from the green menu.
- Click the linked ID in the Order Run column to open the Order Run Details page.
- Click Logs.
Order run log details¶
From the Order Run Logs dialog, you can:
- View information on the execution and outcomes of the order run. For example, failed tests surface as an error in the logs.
- Filter by Log Levels and Node, or use the Search logs field to narrow the list by Message.
- Select RAM and/or Disk to add columns to the log. When checked, the log displays memory and disk space consumption. See Runtime Resources for more information.
- Click Export Logs to download a full log file.
- Admin users only: Click See Details to expand messages and view exception stack traces where available.
Visual example in Automation¶

View node logs¶
From the Order Run Details page, you can select any node to open the Node Details.
Click View Node Logs to open the Order Run Logs with filters applied for that specific node.
Ingredient node order run logs¶
When a variation includes an ingredient node, it can call an ingredient from within the same kitchen or from a different kitchen.
The location of an ingredient determines where the system performs the ingredient processing and how the system handles the log information.
- Ingredient in same kitchen: when the ingredient is located in the same kitchen as the variation, the system processes the ingredient as a separate order within that kitchen. The variation's order run logs have a reference to the ingredient's order run logs.
- Ingredient in different kitchen: when the ingredient resides in a different kitchen from the variation, the system processes the ingredient in a temporary child kitchen of its home kitchen. The system polls the ingredient's logs for 60 seconds, then transfers the log entries to the order run logs of the calling variation.
Logs in the CLI¶
Logs for an order run can be accessed with the orderrun-info command and the --log option.