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

# Test a workflow

> Test a Ravenna workflow safely by publishing it behind a narrow trigger filter, reading each run's resolved inputs and step logs, and replaying runs after a fix.

Drafts can't run, and the builder has no run button. To test a workflow, publish it so it only reacts to test activity, then read every run it produces.

## Testing model

* Draft workflows cannot run by any path: trigger, API, or Ravenna Assistant. Every manual run requires a published (On) workflow.
* There is no sandbox or dry-run mode. Every run executes real side effects: messages, ticket changes, and integration calls.
* Runs whose trigger filters did not match are recorded as skipped and hidden from run lists. An empty run list after a test usually means the test ticket did not match the trigger filters.

## Recommended test loop

1. Narrow the trigger with a test-only filter (a test form, channel, or tag) so real tickets are ignored.
2. Point side-effect steps at safe targets: a test Slack channel, the tester as assignee, test accounts in integrations.
3. Publish, then create a ticket that matches the filter.
4. Inspect each step's resolved inputs, outputs, and log. A completed status does not prove correct behavior; empty or wrong resolved inputs are the most common first-build mistake.
5. After a fix, publish and retry an earlier run with the latest version. It replays the original trigger data against the new version and repeats all side effects.
6. Widen the filter and targets, then publish again.

## Manual runs

* `POST /workflows/{workflowId}/run` on the Ravenna API starts one run of a published workflow and returns the new run ID. The JSON body is delivered to the trigger as the request body, which fits Webhook-triggered workflows.
* Running a workflow on the user's behalf is a real execution. Do not publish a workflow just to make a run possible; publishing is the user's decision. Report that the workflow did not run because it is not published and offer to publish it.

## Waits during testing

* Workspace admins can skip a Wait or Wait Until step on a running run.
* Wait for Approval and Wait for Message continue when someone approves, declines, or replies on the ticket.


## Related topics

- [Workflows](https://docs.ravenna.ai/documentation/automate/workflows/overview.md)
- [Workflow builder](https://docs.ravenna.ai/documentation/automate/workflows/workflow-builder.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.