> ## Documentation Index > Fetch the complete documentation index at: https://docs.connie.ai/llms.txt > Use this file to discover all available pages before exploring further. # Test and run > Test steps safely, run a workflow once, set it live, read run results, retry failures and understand what it costs. Once your steps are in place, you test them one at a time, run the workflow on a few rows, and then set it **live** so it runs by itself. This page covers each stage, plus where to see results and what everything costs. **Where:** open a workflow · `https://connie.ai//workflows/`. Tests are in each step's panel; running and going live are in the top-right of the top bar; results are on the **Runs** tab. ## Test a step A test runs one step so you can see its real output before you run the whole workflow. It also captures sample data that later steps' [variables](/automations/workflows/variables) use. **Tests are real.** A test is not a simulation. Testing **Send Email** sends the email. Testing a LinkedIn step sends the message or connection request. Testing a paid step **spends credits** (from the workspace, charged when you click). While you build, point send steps at your own email address or LinkedIn profile. Click the step's card, then **Test** in the panel footer. The **Test** panel opens with **Input** and **Output** tabs. **Input** ("Confirm or fill variables to run your test") lists every variable the step uses. You can type over a value, or pick a different sample row with **Search a record…**. Required values that are missing must be filled in before you can run. The button shows the credit cost if there is one. A confirmation window explains what the step will do and what it may cost (for example "Costs up to 18 credits"). Click **Run test** to go ahead, or **Cancel**. **Output** shows a **Success** or **Failed** badge and each field with its value. **Copy output** copies it all. The result is saved on the step, so later steps can pick its fields in the variable picker. **What a test uses** * **Row data** comes from the **newest** record on the Records tab, unless you choose another one. * **Earlier steps' data** comes from each earlier step's **last test**, not from a real run. If an earlier step hasn't been tested, you type a value instead. * Free steps that only read data may run straight away without a confirmation. * A test refuses to send if a required field still contains an unfilled variable. If the cost can't be worked out in advance, the confirmation says "This action could not be priced before running." and "Running it may still charge credits. Continue only if you expect that." Some actions also note "A provider used by this action may bill separately." **Test a trigger:** see [Test a trigger](/automations/workflows/triggers#test-a-trigger). ## Pin output **Pin output** tells a step to stop running and reuse its last test result instead. It's handy while building: pin an expensive enrichment step once, then test the steps after it as many times as you like without paying again. 1. **Test** the step first. Until you do, **Pin output** is greyed out: "Test this node first to capture an output you can pin". 2. Step **⋯** → **Pin output**. The card shows a **Pinned** badge: "Pinned — the stored test output will be returned instead of executing this node". **Pin output also applies to live runs.** A pinned step does not run in real runs either: every row, every time, gets the same stored test result. If all your rows show identical data from one step, it's pinned. **Unpin output** (step **⋯** → **Unpin output**) before you set the workflow live or run it on real rows. A pinned step isn't executed, so it doesn't charge credits. ## Run a workflow The **Run** button in the top bar changes depending on the trigger: | Trigger | What **Run** offers | | - | - | | **Run every row of a list** | **All rows**, **First 10 rows**, **First row only** or **Selected rows**, plus **Run only on empty cells** and **Keep running on new rows** (which turns the button into **Run and set live**). | | **Manually** | Opens the **Run flow** panel with your form. Fill it in and click **Run**. | | **Event** or **Schedule** | **Set live** (with a **Run once now** switch) or **Run only once now**, which runs one time without going live. | If **Run** is greyed out, hover it: "Please configure the trigger node" or "Complete all required fields to go live". A red **Missing field** pill in its place means a step still has an empty required field; click it to jump there. **What "run once" uses** * **Event triggers** (email, LinkedIn message, webhook and similar) re-use the captured test event you chose with **Use as test event for Run Once**. If none has been captured, you'll see "No test event captured yet". Capture one first: see [Test a trigger](/automations/workflows/triggers#test-a-trigger). * **Schedule** creates a new row in **Runs**. * **Manually** creates a new row each time. After a run you started, the canvas cards show **Completed**, **Error** or **Skipped**, and a toast reads "Flow finished" or "Flow failed — open run to see why". These canvas badges only appear in the browser tab that started the run; the **Runs** tab always has the full picture. ## Set a workflow live **Live** means the trigger is switched on: events, schedules and new rows start runs automatically. Until then the workflow is a **Draft** (shown as **Idle** on the Automations page) and only runs when you start it. Fill every required field and **Unpin output** on any pinned steps. For a list-based workflow, turn on **Keep running on new rows** and click **Run and set live**. The first time you set a workflow live (except Schedule triggers), the **Settings** window opens. Choose your running hours and click **Done**. If you close it without clicking **Done**, the workflow stays in draft. The top bar shows a green **Live** pill, or **Running** while a run is in progress. Event workflows show "Flow is live — waiting for events". The Automations page shows **Active**. **Messages you may see when going live** * "Please configure your workflow before running" * "Cannot set live: flow has no trigger node" * "Cannot set live: add at least one action node" * `Can't set live — "Find Email" and "Send Email" are missing 2 required fields`: open the named steps and fill the fields marked \*. * "Can't set live — reconnect your account first": click **Reconnect** in the message, reconnect the app on the Tools page, then try again. * `Can't run — "Send Email" has an invalid Email. Fix the value or use a {{variable}}.` * "The account this trigger uses belongs to a different workspace." * A message from a connected app, for example Calendly requiring a paid plan. ### Pause (go back to draft) Hover the green **Live** pill and click **Pause**, or open the **Running** menu → **Stop live**. If you try to change the structure of a live workflow, the "This workflow is live" window offers **Set to draft**. **Pausing cancels every run that's in progress.** Those rows are queued. When you set the workflow live again, they resume and only the unfinished steps run ("Resumed 3 stopped rows"). If there aren't enough credits, you'll see "Flow is live, but stopped rows were not resumed — not enough credits for the batch." and the rows stay queued. While a workflow is live you can still edit settings inside steps, but not add, move or delete steps. See [Editing a live workflow](/automations/workflows/build#editing-a-live-workflow). ## Workflow settings Click the gear icon (**Workflow settings**) in the top bar. The **Settings** window: "Apply settings to schedule your workflow." It's not shown for Schedule triggers; their card holds the same settings. * **Rules** * **Stop flow if node fails** (on by default): a failed step stops the rest of that run. See [When a step fails](/automations/workflows/logic#when-a-step-fails). * **Queue triggers outside of window** (on by default): events that arrive outside your running hours wait until the window opens. If you turn it off, those events are not run. * **Running hours:** **24/7**, **Mon-Fri (9 to 5)** or **Custom** (turn days on and off, set time ranges, **Add new time**, **Apply to all days**). Ranges can't cross midnight. * **Time zone** for the running hours. * **List sync** (list-based workflows): for each mirrored list, "When on, records added to this list are mirrored into the flow automatically." Running hours apply to event and webhook runs, not to Schedule triggers. If your LinkedIn steps would go over your LinkedIn account's daily limits with these hours, Connie suggests a schedule; you can accept it or click **Keep my settings**. Click **Done** to save. ## The Runs tab **Runs** is a read-only grid of results: one row per run (for list-based workflows, one row per list row) and one column per step. The first columns show the record and when the trigger fired. Each cell is that step's **latest** result for that row; running a row again replaces it. | Cell status | Meaning | | - | - | | **Success** | The step worked. Loops show e.g. "Success: 12 of 12". | | **Failed** | The step failed. Click it to see why. | | **In progress** / **Queued** | Running now / waiting its turn. An AI Agent shows "Thinking...". | | **Waiting** | Inside a **Delay**. | | **Needs approval** | Waiting for someone to approve. See [Require approval](/automations/workflows/logic#require-approval). | | **Rejected** | An approver rejected it. | | **Condition not matched** | A Router branch that this row didn't take. | | **Skipped** | Not run because an earlier step failed, or a loop had no items. | | **Partial** | Some loop items succeeded and some failed. | | **Node deactivated** | The step is switched off. | | **Sent**, **Replied**, **Accepted** | Outreach steps' progress. | **See the details:** click a cell to open **Cell Details**, with **Input** (what went in, with variables filled) and **Output**. **Copy as JSON** copies it. ### Fix and retry a failed step Click a **Failed** cell. The **Execution Failed** panel shows the error, the inputs it used, and these options: * **Fix with AI:** Connie suggests a fix. * **Edit configuration:** opens the step's settings. * **Retry** → **Retry this node** ("Re-run only the failed cell") or **Retry this row** ("Re-run the failed and empty cells"). Retrying a row runs it from the top but only fills failed, skipped and empty cells; steps that already succeeded aren't repeated, "so nothing is sent twice". * **Restart this flow** (for some sending-account errors) and **Upgrade plan** (for credit errors) appear when relevant. ### Re-run rows On **Records** or **Runs**, tick the rows, then **Run** → **Run selected rows** → **Run all selected** or **Run only empty cells**. Rows that are already running are skipped: "The flow is already running on these rows. Stop them first if you want to rerun them." ## Stop a run * **One run you started:** hover **Running** and click **Stop** ("Flow stopped"). * **Manual workflow:** **Running** menu → **Stop run** ("Stopped 2 flow runs"). * **Specific rows:** tick them → **Running** menu → **Stop selected rows (N)**. * **Everything, and stop automatic runs:** **Stop live** / **Pause**. ## Credits **Credits** are Connie's usage currency. See [Credits](/billing/credits) for balances and plans. * **Each paid step charges its price every time it runs, once per row.** Example: a workflow with a 1-credit step and a 2-credit step, run on 100 rows, costs up to 300 credits. * **Free:** Router, For each, Delay, the LinkedIn checks, Formula, data helpers and Records actions. * **1 credit per run** for common steps such as **Send Email**, most LinkedIn sends, **Api Call**, **Scrape Web** and **Search Internet**. Enrichment varies by action. AI image, audio and video steps cost from about 100 to 1,000 credits. * **Run AI agent** (the AI Agent step): a 1-credit step fee **plus** AI usage **plus** any paid tools it uses. That's why the picker shows "From N" rather than a fixed price. **AI Analyzer** and AI-written fields are billed by AI usage. * **Inside a For each,** paid steps charge once per item. * **Tests charge** just like real runs. **Pinned** steps don't charge. * **Failed steps are refunded.** Credits are set aside before a step runs and returned if it fails. * **Run only on empty cells** avoids paying again for cells that already have a result. **Before a run, Connie checks your balance.** At zero or below, nothing runs. If your balance is above zero but below the total price of the workflow's steps, you'll see the **Insufficient credits** window: "This flow requires N credits but your current balance is M.", with **Current balance**, **Required**, **Shortfall** and **Tools in this flow**. This check counts each step once and leaves out AI usage, so a long loop or an AI Agent can still run out partway. When that happens, the cell reads "Insufficient credits to run this tool. Please top up and retry." and the run stops. Owners and admins can see credits spent per record and in the usage log. See [Credits](/billing/credits). ## Good to know * **Who can run:** testing, running, setting live, retrying and stopping all need **Can edit** access to the workflow. View-only users see "You are in view-only mode". * **Failure alerts** go to workspace **owners and admins**, not to the workflow's creator unless they're an admin: a bell notification and an email such as "Your flow 'Lead enrichment' hit an error", at most once an hour per workflow. Running out of credits and stopping a run don't send alerts. Change this under **Workflow run failures** in [Notifications](/notifications/overview). * **Large runs** process rows in batches of about 20 at a time. * **No run limit per workspace,** apart from 500 selected rows per run and your credits. * **How long results are kept:** run results stay as long as their record exists. Deleting a record removes its results. * **The Runs count** on the Automations page is the total number of runs. ## Troubleshooting **Why:** Tests run the step for real. **Fix:** Use your own address or profile while building. Pin the output of steps you've already tested. **Why:** That step's output is pinned, and pinned output is used in live runs too. **Fix:** Step **⋯** → **Unpin output**, then re-run the rows with **Run only empty cells** off. **Why:** The step has no test result yet. **Fix:** Click **Test** on that step first. **Why:** Running once on an email, LinkedIn message or webhook trigger needs a captured sample event. (The message mentions Listen for test event; the button is called **Run Test**.) **Fix:** Open the trigger → **Run Test**, send a real event, then choose it with **Use as test event for Run Once**. **Why:** The first time you go live, you need to save the workflow settings. **Fix:** Choose **24/7** or **Mon-Fri (9 to 5)** and click **Done**. Closing the window keeps the workflow in draft. **Why:** A step or the trigger uses an app account that's disconnected. **Fix:** Click **Reconnect**, reconnect on the Tools page, and set live again. See [Connect accounts](/tools/connect-accounts). **Why:** Required fields are empty in the steps named in the message. **Fix:** Click the red **Missing field** pill to jump to each one and fill it in. **Why:** Going to draft cancels every run in progress and queues those rows. **Fix:** Set the workflow live again. Queued rows resume, and only the unfinished steps run. **Why:** Your balance can't cover the queued rows. **Fix:** Add credits ([Top-ups](/billing/top-ups)), then pause and set live again. **Why:** The other rows were already running and weren't restarted. **Fix:** Use **Stop selected rows**, then run them again. **Why:** **Run only on empty cells** was off. **Fix:** Turn it on in the **Run** menu next time. **Why:** Your balance is too low for this workflow. **Fix:** Add credits or upgrade. Members who can't buy credits can send a request to an admin from the same window. See [Credits](/billing/credits). **Why:** **Running hours** are limited and **Queue triggers outside of window** is on. **Fix:** Set **Running hours** to **24/7** in Workflow settings. **Why:** **Queue triggers outside of window** is off, so those events were dropped. **Fix:** Turn queueing on, or switch to **24/7**. **Why:** For some triggers, running once re-uses the first row instead of adding a new one. **Fix:** Expected. To keep results, run on new rows or duplicate the workflow for testing. **Why:** Badges only show in the browser tab that started the run. **Fix:** Check the **Runs** tab. **Why:** Failure alerts go to workspace owners and admins. **Fix:** Expected. Check the **Runs** tab, or ask an admin to change your role. ## Related * [Build a workflow](/automations/workflows/build) — steps, saving and the live lock * [Variables](/automations/workflows/variables) — why a value comes out empty * [Logic and control](/automations/workflows/logic) — error handling and approvals * [Credits](/billing/credits) — balances, usage log and plans * [Workflow troubleshooting](/automations/workflows/troubleshooting) — more fixes This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.