Demo build. All companies, metrics, messages, and tasks are placeholder data. Nothing connects to a backend; nothing you click writes to a database.

Operations

System-wide health, autonomous ops layer status, recent activity.portfolio →

Self-heal updated: 2026-06-26T15:42:18
7/8 crons installed
0 services not OK

Service health (sovi-self-heal)

ServiceKindStatusDetail
No probe data yet. (In a real deployment, the self-heal cron writes a probe report every 5 min.)

Cron + scheduler installs

INSTALLED
self-heal
active
INSTALLED
dispatcher-retry
active
INSTALLED
afk-watcher
active
INSTALLED
book-pipeline
active
INSTALLED
ceo-chain-morning
active
INSTALLED
ceo-chain-evening
active
INSTALLED
content-engine
active
STAGED (sudo needed)
content-engine-weekly-video
pending

Recent dispatcher retry activity

2026-06-26 15:35:02 INFO retrying task t-aurora-2034 (attempt 2/3)
2026-06-26 15:35:08 INFO task t-aurora-2034 succeeded on retry
2026-06-26 14:18:41 WARN task t-helix-1117 hit rate limit, backing off
2026-06-26 14:23:51 INFO task t-helix-1117 succeeded on retry
2026-06-26 11:02:14 INFO retrying task t-verde-0892 (attempt 2/3)
2026-06-26 11:02:19 INFO task t-verde-0892 succeeded on retry
2026-06-26 08:44:33 WARN task t-tideline-0344 timeout, queuing for retry
2026-06-26 08:49:36 INFO task t-tideline-0344 succeeded on retry

This page reads filesystem state directly. For deeper diagnostics:

  • Full self-heal history (log file on the host)
  • Full dispatcher retry history (log file on the host)
  • Failed task queue (database table)
  • Open circuit breakers (database table)