Scheduling TEDI Automations

Save launch parameters and optional timing so a playbook or monitor runs unattended. The TEDI Windows Service polls for due work and queues it—even when the desktop window is closed.

On Desk, schedule lives on the playbook or monitor rail item (Timing and Delivery tabs). Desk Add has no Schedule card. TEDI still has a Schedules route for playbook schedules.

A schedule may have no timing rules only while it is disabled. Enable requires at least one rule.

Before you start

• You have successfully run the playbook once manually (recommended).
• License is active and your plan still allows the automation you want to schedule.
• The TEDI Windows Service is Running.
• You know the launch parameters that should apply every time (company, folders, batch month, and so on).

Schedule on Desk (playbook or monitor rail item)

1. Open the playbook or monitor rail item in the workspace.
2. Set parameters on the item (playbook Parameters; monitor parameters on that instance).
3. Open the Timing tab.
4. Select Add Rule when you are ready to enable.
5. Choose Rule type: Interval, Hourly, Daily, Weekly, or Monthly.
6. Set the rule fields (every N minutes, time of day, weekdays, day of month, and so on).
7. Keep the rule Enabled unless you want it paused while keeping other rules.
8. Add more rules if the same item should fire on multiple patterns (it runs when any enabled rule is due).
9. Open Delivery if email, Teams, or desktop delivery should go out with the run.
10. Check Enabled on the item only after at least one rule exists, then Save.

Expected outcome: The rail item is a saved TEDI schedule (playbook) or monitor instance (monitor). Timing and delivery stay on that item.

Desk Add can pin a playbook with no rules while it stays disabled. The Timing tab states: Add at least one rule to enable scheduling. Enabling with no rules fails.

For monitors, timing also lives on the instance. See Setting up TEDI Monitors.

Open Schedules in TEDI

TEDI still owns playbook schedules on its own Schedules route.

1. In the TEDI left sidebar, select Schedules.
2. Select Add Schedule.

Expected outcome: The schedule form opens with tabs Setup, Timing, Parameters, and Delivery.

You can also start from Command Center by selecting the schedule (timer) action on an automation card—the form opens with that playbook pre-selected.

Step 1: Setup (TEDI)

On the Setup tab:

1. Choose the Playbook.
2. Enter a Schedule name.
3. Leave Enabled checked only when at least one Timing rule exists and you want the service to run this schedule automatically.

Hint in the UI: TEDI polls every minute when the runner is active. For production, “runner active” means the TEDI Windows Service is Running.

Step 2: Timing rules (TEDI)

1. Open the Timing tab.
2. Select Add Rule (required before you enable).
3. Choose Rule type: Interval, Hourly, Daily, Weekly, or Monthly.
4. Set the rule fields (every N minutes, time of day, weekdays, day of month, and so on).
5. Keep the rule Enabled unless you want it paused while keeping other rules.
6. Add more rules if the same schedule should fire on multiple patterns (the schedule runs when any enabled rule is due).

Expected outcome: Each rule card shows a readable summary.

Timing tips

• For a first test, use a Daily or Interval rule a few minutes ahead, save, then watch Command Center → Next scheduled runs or Schedules → Up next.
• Unchecking schedule-level Enabled pauses the whole schedule (card shows Paused) even if rules are enabled.
• Next run follows the schedule timezone.

Step 3: Parameters and Delivery (TEDI)

1. Open the Parameters tab.
2. Set the playbook inputs this schedule should use each time it runs — the same fields you would fill for a manual run.
3. Double-check Company, folders, and month fields that change over time.
4. Open Delivery to optionally send email or Teams when a scheduled run finishes.

Save, verify, and Run Now (TEDI)

1. Select Create Schedule (or Save Changes when editing).
2. Confirm the success message Schedule saved.
3. On the schedule card, check Enabled, Next run, and Timezone.
4. Optionally select Run Now to queue immediately without waiting for the next rule time.

Expected outcome: The schedule appears on Schedules and under Command Center next-scheduled panels. Run Now shows a queued-run confirmation.

On Desk, use Execute on the playbook rail item for the same immediate queue.

Keeping schedules healthy

• Windows Service must stay Running — Closing the desktop app does not stop schedules; stopping the service does.
• Tray minimize is optional convenience for the desktop UI; it is not a substitute for the service.
• After saving, confirm the schedule appears in Up next / Next scheduled runs before relying on overnight runs.
• Use Edit (TEDI Schedules) or Save on the Desk rail item to adjust timing or launch parameters; use Delete only when you intend to remove the schedule (confirm dialog: Delete this schedule?).

Common mistakes

• Service stopped — Enabled schedules will not fire if TEDI Runner is not Running.
• Enabled with no timing rules — Empty rules are allowed only while the schedule is disabled. Enable requires at least one rule.
• Looking for a Schedule card on Desk Add — Automations is Activity, Playbooks, and Monitors. Timing lives on the rail item.
• Paused schedule — Enabled unchecked on Setup means the card shows Paused.
• Stale launch parameters — Folder paths and batch months saved on Parameters must stay valid over time.
• Wrong timezone — Next run follows the schedule timezone, not necessarily your wall-clock assumption.

Next steps

• Understanding Run Results and Proof Packs — Review what each scheduled run produced.
• Setting up TEDI Monitors — Instance timing is on the monitor pin, not a separate Schedule rail.
• Monitoring and Troubleshooting TEDI — When a schedule never appears in Up next or never runs.
• Running a TEDI Automation — Manual queue path for one-off jobs.