Skip to main content
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.
Every run does real work. It sends the messages, changes the tickets, and calls the integrations the workflow is wired to. Point those steps at safe targets while you test.

Test with a narrow trigger filter

1

Choose a test-only signal

Filter the trigger to something only your test tickets have, such as a test form, a test channel, or a tag like workflow-test. Real tickets won’t match, so the workflow ignores them.
2

Point side effects at safe targets

While you test, send messages to a test Slack channel, assign tickets to yourself, and use test accounts in integration steps.
3

Publish the workflow

Turn on the switch in the editor. Learn more about publishing.
4

Trigger it with a test ticket

Create or update a ticket that matches the filter, for example by submitting the test form or adding the test tag.
5

Read the run

Open the workflow’s Runs tab and select the run. Select each step to see its status, inputs, outputs, and log.
6

Widen the filter

When the runs look right, change the filter and targets to the real ones and publish again.

Read the run, not just the status

A run can finish as Completed and still do the wrong thing. For every step, check:
  • Inputs: the values the step actually used, after dynamic values resolved. An empty ticket ID or a blank message body means a dynamic value pointed at the wrong field.
  • Outputs: what the step produced for later steps.
  • Log: what happened while the step ran, including why a step was skipped.
If no run appears at all, the trigger fired but its filters didn’t match your test ticket. Runs whose trigger filters didn’t match aren’t listed. Check the filter against the ticket.
Learn more about runs and step logs

Retest after a change

You don’t need a new test ticket every time you fix something. After you publish a fix, replay an earlier run against the new version:
  1. On the Runs tab, open the row menu of a run that showed the problem and select Retry.
  2. Choose Retry with latest version. The new run starts from the first step with the original trigger’s data, using the version you just published.
The replay repeats every step’s side effects, such as messages and ticket changes.
Learn more about retry options

Test wait and approval steps

  • Wait and Wait Until: a workspace admin can select Skip Wait on the waiting step in the run to continue immediately. See Skip wait steps.
  • Wait for Approval: while you test, make yourself the approver in the step that adds the approval round, then approve or decline the test ticket to try each path.
  • Wait for Message: reply on the test ticket to continue the run.

Run a published workflow through the API

You can start a run of a published workflow from the Ravenna API. This suits workflows with a Webhook trigger, because the JSON you send becomes the request body the trigger receives.
The response contains the new runId. Paused and draft workflows return a not-found error.You can also ask Ravenna Assistant to run a published workflow. It starts a real run, the same as the API.
Last modified on November 18, 2026