Skip to main content

​
Overview

Run an existing Triggered Workflow at specific times using a Scheduled Workflow.

​
How it works

  • A Scheduled Workflow finds tickets via filters
  • It triggers your existing Triggered Workflow for each ticket
  • The Triggered Workflow runs exactly as designed

​
Setup

1

Create the scheduled workflow

Name it “Scheduled [Triggered Workflow Name]” and set your cadence (daily at 8AM, hourly, one-time via Run Now).
2

Filter tickets

Add precise filters (e.g., New + Unassigned; Board = Help Desk; Created ≤ 7 days).
3

Add Trigger Another Workflow

Pick the target Triggered Workflow. Set bypassing of filters depending on whether you want double filtering.

​
Use cases

​
Morning dispatch

Dispatch overnight tickets before the day begins.

​
Apply to existing tickets

Run a new Triggered Workflow against the last 7 days of tickets.

​
Off-peak batch processing

Run heavy workflows at night to reduce daytime load.

​
Best practices

  • Test first with Run Now and a small set
  • Use time-bounded filters to avoid reprocessing
  • Monitor results in Event History and tune schedule
Make sure a ticket can leave your filter. The scheduled workflow re-runs its filter on every tick, so any ticket that still matches gets triggered again. If the target is meant to act once, either turn on Run only once per ticket on it, or filter on something the run itself changes (a status, or a custom field the agent writes).The trap is the second option failing quietly: if the agent skips that write — no data to compute a value, a condition not met — the ticket keeps matching and is re-triggered every cycle until you notice. Watch Event History for the same ticket number repeating at your schedule’s interval.