Operations
The Operations console is where you run and watch a project’s background jobs — the work that turns incoming communications into registers, the graph, and health. You reach it from a project’s admin area; it shows live counts and refreshes every few seconds.
Most work is split into self-describing operation cards. Each card tells you what it does, whether it acts on This project or the Whole workspace, whether it calls an LLM (No LLM, Haiku, or Sonnet), and — for LLM jobs — a cost estimate before you run it. Cards that don’t use an LLM are marked Free; LLM cards show ”≈” or “up to” a dollar figure. Once an op has run, its estimate is calibrated from your real usage history; until then it shows an uncalibrated estimate.
What a backfill is for
Section titled “What a backfill is for”A backfill replays existing data to catch something up — for example after you connect a source, enable a module, or fix how a piece of data is derived. The backfills here are idempotent: safe to re-run, because already-applied work is skipped. (A backfill differs from a reconcile, which corrects drift without reprocessing everything — see the Glossary.)
The tabs
Section titled “The tabs”Pipeline
Section titled “Pipeline”Controls the classify queue for this project. Reclassify all re-runs the classifier on every item (the most expensive action here — one Sonnet call per item plus one per attachment; ClickUp items are excluded). Retry failed / stuck resets failed items and zombies (stuck classifying for more than 15 minutes) back to the queue, re-running the Sonnet classifier on each. Cancel pending classify, Clear failed jobs, and Reprocess attachments are free queue operations.
Queues
Section titled “Queues”Live status of the classify and attachment-ingest queues (waiting, active, delayed, failed, completed), a breakdown of items by status, and lists of any stuck or failed items you can re-run individually.
Backfills
Section titled “Backfills”The idempotent maintenance jobs, including Backfill sentiment (score every not-yet-scored message), Backfill action owners (populate My work), tag seeding and tagging, and several one-off repairs. Workspace-wide backfills (the graph backfill, and the user-email and stakeholder-link backfills) live on the Workspace operations page.
Relations
Section titled “Relations”Classify and resolve relationships between event-register items — duplicate, supersedes, contradicts, relates — per register kind (decisions, risks, issues, action items, meetings), or for all kinds at once. Classify uses an LLM (Haiku); resolve does not.
Hygiene
Section titled “Hygiene”Retire stale items — archive still-open items that are long overdue or years old out of your work surfaces (My work, Project work, the registers, and overdue counts). They’re retired, not deleted: each row stays in the graph and on its detail page, and you can un-retire any of them. Applies to action items, risks, issues, and decisions. Preview the counts before you commit.
Replay
Section titled “Replay”Re-feed a project’s source data — raw emails (Postmark webhook JSON) and bulk-imported .eml files kept in object storage — back through the ingest and classify pipeline. Plan replay previews what would run; Execute replay enqueues it. Items already present are skipped.
Danger
Section titled “Danger”The isolated factory reset. It deletes this project’s derived data (ingested items, registers, evidence links, attachment metadata, documents, audit log) and writes a recovery manifest to object storage first. Original source data is untouched, so you can rebuild with Replay.