> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oviond.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test an automation

> Send an automation immediately to verify its content.

A **test send** bypasses the schedule and emails the report right now. Use it after creating or editing an automation — it's the fastest way to catch a broken widget, wrong logo, or mangled subject line before a real delivery.

<Steps>
  <Step title="Open the automation">
    From the **Automations** list, use the row menu or open the details slide-over. You can also test from the **Automations** tab inside the project editor.
  </Step>

  <Step title="Click Test">
    Oviond renders the report with the automation's current settings and sends it exactly as a scheduled run would.
  </Step>

  <Step title="Confirm the recipients">
    The recipient dialog is pre-filled with the automation's saved recipients. Edit them to send the test to a different address instead.
  </Step>

  <Step title="Check the inbox">
    Verify the subject, sender, message body, and rendered report look correct.
  </Step>
</Steps>

A test runs immediately rather than going through the queue, so you get fast feedback. Oviond also posts a success or failure notification when it finishes.

<Note>
  A test send does **not** advance the automation's schedule — it leaves the last-run and next-run times untouched. It **does** record an entry in [run history](/automations/history), flagged as a **Test** run so you can tell it apart from scheduled deliveries.
</Note>

<Warning>
  You can't test a **paused** automation — the **Test** action is disabled until you resume it.
</Warning>