Choose the environment a test runs in

Test in: at the top of the designer decides which values a test reads from your variables — Development (sandbox values) or Production (your real services). Live runs always use Production.

Who can do this

Workspace Admins and Editors, on Starter and above. On Free the button is greyed out and fixed on Production: Your workflows keep running on Production values. Upgrade to change variables or to test in Development.

Steps

1. Open the workflow in the designer.
2. Select Test in: at the top right. It shows the environment in use.
3. Choose Development or Production.

When Production is chosen, the menu warns This test calls your real services — Production values are used., and a strip across the canvas says This test calls your real services — Production values are used. Rows will be added and messages sent for real.

What happens next

• Your choice is remembered for you, on this workflow, on any device. Someone else testing the same workflow has their own.
• Test run and Run this step read variables in the chosen environment, and a step with a Connection variable uses that environment's connection.
• The variable warnings on steps follow it: api_base_url has no Development value. appears only while testing in Development.
• Publish always checks Production, whatever is chosen here.

Good to know

• New workflows test in Development until you choose otherwise.
• Schedules, webhooks, forms and app triggers always run in Production.
• Run the live version now asks which environment each time, with Production chosen. See Run the live version now.
• Lists have no environments. A test writes to the same list a live run does.

If something goes wrong

Related

• Manage a workflow's own variables
• Testing a workflow before you publish it
• Variables and environments