Scheduling TEDI Automations

Create a schedule so an approved playbook runs on a recurrence with saved launch parameters. The TEDI Windows Service polls for due schedules and queues the work—even when the desktop window is closed.

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).

Open Schedules and start a new schedule

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

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

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

On the Setup tab:

1. Enter a Schedule name.
2. Choose the Playbook.
3. Set Timezone (default is often America/New_York—confirm it matches how you think about the run time).
4. Leave Enabled checked when 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

1. Open the Timing tab.
2. Select Add Rule (add at least one rule).
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.
• Confirm timezone on Setup before trusting Next run.

Step 3: Launch parameters

1. Open the Launch tab.
2. Set Override launch parameters for this schedule — the same fields you would fill for a manual run.
3. Double-check Company, folders, and month fields that change over time.

Save, verify, and Run Now

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.

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 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.
• No timing rules — Save requires at least one rule.
• Paused schedule — Enabled unchecked on Setup means the card shows Paused.
• Stale launch parameters — Folder paths and batch months saved on Launch 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.
• 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.