Order Runs¶
Each order contains at least one order run. Order runs represent the distinct, one-time processing of a recipe variation in a kitchen.
An order can be associated with multiple order runs if the order was scheduled with some degree of repetition. For example, an order that is set to run daily generates a distinct order run record each day.
Each order run is given an order run ID that is globally unique in this Automation tenant. Each order run has its own URL.
Example order run ID
802213bc-3662-11e9-9f7b-0ad19868a29a
Tip
Share the order run URL with teammates for better visibility and collaboration.
Example URL
https://cloud.datakitchen.io/dk/orders/im/im_production/runs/e2eb2890-c28f-11ed-802a-5a5102f60c95
Order run details¶
Order run data and results display on the Order Run Details page. From the Orders page, select any Order Run ID to open the order run details.
Each order run record includes the following data:
- An identical copy of the recipe code and configuration that was processed.
- All parameters and runtime variables with their compiled values per the override hierarchy.
- Access to the order run logs.
- Identification of data inputs and outputs.
- Identification of leveraged infrastructure instances.
- Test result metadata.
- Process timing metadata.
The same data can be accessed by the command line.
With this information, order run records can help in back-testing use cases and are often suitable to meet governance and regulatory requirements.
Note
Order runs history: Automation maintains the order and order run data of inactive orders for three months, after which time the data is deleted. Data for active orders is retained. Deleting a kitchen without promoting its order runs to a parent kitchen deletes all data—active or not.