Run Recipes

Save Flow filters and Value overwrites so you can start the same Run again.

A Run Recipe is a saved Run setup: which Flows and Test Cases to include, plus any Value overwrites. Use one when the same selection should start from Settings, a Schedule, or CI / CD.

Create and manage recipes under Settings → Run Recipes. Open a recipe to edit it, or use Run to start it straight away.

When to use a Recipe

• Start the same smoke or staging selection without re-picking tags each time.

• Point Schedules and CI at one recipe so every trigger stays aligned.

• Overwrite Values for an environment without editing each Flow.

• Iterate a list of Value sets, such as country or currency variants, in one recipe.

Create a Recipe

1

Open Run Recipes

Go to Settings → Run Recipes, then create a new recipe and give it a clear Title.

2

Choose Flow filters

Control which Flows are included:

Filter	What it means
Include Tags	The Flow must have all of the selected tags
Exclude Tags	The Flow must have none of the selected tags

Tags usually come from Tag Test on each Flow Branch. See Build smoke and regression coverage.

3

Choose Test Case filters

Optionally narrow Test Cases inside the matching Flows with the same include and exclude tag rules.

4

Set Value overwrites

Add key-value pairs that replace matching account Values from Assets → Values for this Run. When Start Run, DoesQA Run, or CI/CD body Values set the same name, those this-run Values win. Full order: Value Store.

Example:

{
  "BASE_URL": "https://staging.example.com",
  "USERNAME": "testuser123",
  "COUNTRY": "UK",
  "FEATURE_FLAG_CHECKOUT_V2": true
}

Use overwrites for environment URLs, credentials, regions, or feature flags without editing the Flow.

Pro tip: Name recipes after the job they do, such as Smoke - Staging or Checkout - UK DE FR, so Schedules and CI keys stay obvious.

Iterate over Value sets

Provide an array of objects in Value Overwrites when the same Flows should run once per data set. Each object is one pass with its own Values.

Set primaryValue inside each object when you want results to show which data set ran.

[
  {
    "primaryValue": "United Kingdom",
    "COUNTRY": "UK",
    "USERNAME": "user_uk",
    "BASE_URL": "https://uk.example.com",
    "CURRENCY": "GBP"
  },
  {
    "primaryValue": "Germany",
    "COUNTRY": "DE",
    "USERNAME": "user_de",
    "BASE_URL": "https://de.example.com",
    "CURRENCY": "EUR"
  },
  {
    "primaryValue": "France",
    "COUNTRY": "FR",
    "USERNAME": "user_fr",
    "BASE_URL": "https://fr.example.com",
    "CURRENCY": "EUR"
  }
]

In this example the recipe runs the selected Flows three times: once for the UK, once for Germany, and once for France.

Related

• Schedules

• CI / CD

• Value Store

• Tag Test

• Build smoke and regression coverage

• Run across environments

• Max Concurrency