Configure Alert Thresholds

The alerts for test warnings and order runs exceeding a time limit require threshold settings at the variation level, regardless of where the alerts are configured (i.e. at the kitchen or recipe level).

Warning

Time limit exceeded and warning alerts configured for recipients in a kitchen or in a recipe will not send unless the order's variation has thresholds configured for the time limit and/or a number of test warnings to trigger those alerts.

Set time and warning thresholds

1. Navigate to the alert thresholds form.
   • From the Recipes page, select a recipe from the list. Select the Variations tab, then click Actions for the relevant variation. Select Edit Alert Thresholds.
   • From the Variation page, select the Alert Thresholds tab.
2. Under Time Limit:
   • Select minutes or hours to define the unit of time.
   • Enter the number of minutes or hours allowed for an order run to process.
   • Use the radio buttons to send the alert only or to stop the order run and send an alert.

3. Under Test Warnings Threshold, enter the number of warnings that can be created by node tests before an alert is triggered.

   Note

   Warning counts reset on resumed order runs. An order run that stops on a test failure and has collected warnings from upstream nodes does not continue that count of warnings when the order run is resumed. Instead, the warning count resets to zero for the resumed run.

4. Select Add notes for changelog , describe the changes, then click Update.

Visual example in Automation

variations.json

You can switch to the File Editor for the recipe to edit the variations.json file manually.

From the Recipes page, select Recipe Actions > View Files, then select the variations.json file.

{
    "variation-list": {
        "my_variation": {
            "graph-setting": "graph_to_run",
            "minutes-to-timeout": 60,
            "action-on-timeout": "warn" | "stop",
            "warnings-count-threshold": 10,
        }
    },
    ...
}