Skip to main content
Share / Export

Monitoring and Troubleshooting TEDI

Use Command Center and Recent Runs to see what ran, what is next, and what needs attention. This article covers day-to-day monitoring and the failures teams hit most often.

Where to look first​

  • Command Center — License, Active Schedules, Active Runs, Next Scheduled, recent runs, upcoming schedules, automation library snapshot.
  • Recent Runs — Step progress, Failed / Blocked detail, retry, proof packs.
  • Schedules — Enabled vs Paused, Next run, Run Now.
  • Windows Services — Confirm TEDI / TEDI Runner is Running.
  • C:\ProgramData\TEDI\artifacts\ — runner-runtime.log and per-run evidence when the UI message is not enough.

Command Center overview with metrics, attention alert, recent runs, and next scheduled

Command Center checklist​

  1. Open Command Center.
  2. Confirm License is active.
  3. Check Active Schedules counts match what you expect enabled.
  4. Review Next Scheduled / Next scheduled runs.
  5. Review any banner that playbook run(s) need attention → Review runs.
  6. If you see API probe failed, wait for the desktop local API to come up, restart the desktop app if needed, and confirm the service is healthy.

Command Center metrics row showing License, Active Schedules, Active Runs, Next Scheduled

Healthy vs unhealthy signals​

  • Healthy: License active, Windows Service Running, catalog loaded, Next scheduled populated for enabled schedules, Recent Runs completing, no attention banner.
  • Unhealthy: License not activated, service stopped, catalog not loaded, schedules Enabled but never appearing next, repeated Failed/Blocked runs, API probe failed.

Troubleshooting by symptom​

Windows Service stopped / schedules never fire​

  1. Open Services.msc and confirm TEDI (TEDI Runner) is Running.
  2. Start the service if it is stopped.
  3. Confirm the schedule card shows Enabled (not Paused) and has a future Next run.
  4. Use Run Now once to prove queueing works.
  5. If it still fails, check C:\ProgramData\TEDI\artifacts\runner-runtime.log.

Remember: closing the desktop app does not stop schedules. Stopping the Windows Service does.

Windows Services showing TEDI Runner stopped or running

License blocks automation​

  1. Open Settings → License.
  2. Confirm Status / Plan / Valid until.
  3. Select Verify license (requires network access to tuds.ai).
  4. If the plan caps active playbooks, disable unused automations or upgrade.

License Status panel when subscription is inactive or expired

Catalog not loaded / automations missing​

  1. Open Settings → Database.
  2. Confirm connection settings, then Save connection.
  3. Select Refresh catalog from SQL Server.
  4. Expect Local Vista catalog is loaded.
  5. If refresh fails, fix ODBC driver, server name, credentials, and firewall, then retry.

API probe failed / desktop cannot talk to local API​

  • Give the app a few seconds after launch, then reopen Command Center.
  • Quit the desktop from the tray and launch TEDI again from the Start Menu.
  • Confirm nothing else is blocking local port communication used by the desktop API (default host/port is local-only).
  • Admin check: C:\ProgramData\TEDI\python\Scripts\tedi-runner.exe self-check

Run Failed or Blocked​

  1. Open the run in Recent Runs.
  2. Read the failed/blocked step message in Step progress.
  3. Fix Vista state, folders, or data as indicated.
  4. For Failed, use Retry from failed step after the fix.
  5. For Blocked validation stops, correct the business condition and queue a new run.
  6. Open View proof pack when available for evidence.

See Understanding Run Results and Proof Packs for status definitions.

Manual Queue Automation fails immediately​

  • License inactive or catalog not loaded.
  • Required launch fields blank or invalid.
  • Vista not available / wrong company / user cannot access the company.
  • Service or runner unhealthy — check service status and runner-runtime.log.

App “closed” but you still need the UI​

  • Default Minimize to tray — tray tooltip TEDI - automation running in background.
  • Reopen with tray Open TEDI or double-click the tray icon.
  • Tray Quit exits the desktop app; the Windows Service should still run schedules.

Log files and data locations​

  • C:\ProgramData\TEDI\artifacts\runner-runtime.log — Runner / service host log
  • C:\ProgramData\TEDI\artifacts\runs\ — Per-run evidence folders
  • C:\ProgramData\TEDI\data\ — SQLite stores (runs, schedules, license cache)
  • C:\ProgramData\TEDI\cache\ — Vista catalog cache
  • C:\Program Files\TEDI\service\TediRunner.Service.exe — Windows Service host

When opening a support case, include the approximate run time, playbook name, step title/message, proof pack if any, and a matching log snippet.

File Explorer open to C ProgramData TEDI artifacts folder

Quick recovery order​

  1. Windows Service Running?
  2. License active?
  3. Catalog loaded?
  4. Vista usable on this machine for the target company?
  5. Schedule Enabled with timing rules and a future Next run?
  6. Read Recent Runs step message + proof pack / logs for the specific error.
  • Getting Started with TEDI — Desktop vs Windows Service
  • TEDI Initial Setup — License and database catalog
  • Running a TEDI Automation / Scheduling TEDI Automations — Happy-path configuration
  • Understanding Run Results and Proof Packs — Failed, Blocked, retry, proof packs