Agent Schedules & Cron Jobs

Every recurring job across the WebXpress agent fleet — what runs, how often, and where it actually lives (Cowork scheduled task vs. droplet crontab vs. not confirmed at all). Times shown in IST with the underlying UTC cron alongside.

Sara DigitalOcean droplet crontab — 139.59.24.166

Root crontab on the droplet, driven by sara_run.sh <mode>. Not visible or pauseable from Cowork — SSH-only.

JobCadenceIST timeUTC cronWhat it doesStatus
Jira mirror syncEvery 15 minContinuous*/15 * * * * Syncs Jira into local Postgres mirror (fed from Supabase) — the data source for chase/digest/weekly Live
Chase / nudge engineMon–Fri10:30 IST0 5 * * 1-5 Scans stuck Jira items, nudges owners directly by email, escalates to CEO after 3 unanswered nudges or no resolvable owner Live since 14-Jul-2026
Mail-gap / Teams-gap checkMon–Sat~10:35 IST~5 5 * * 1-6 Flags threads/Teams chats gone quiet — feeds Mira's PM-silence cross-reference Live
Email/inbox ingestEvery 10–15 minContinuous*/10-15 * * * * Reads apurva@ + support@webxpress.in via Microsoft Graph, feeds the temperature/scoring model Live
Daily heat-map digestDaily08:00 IST30 2 * * * Heat-map digest of open support threads to CEO Disabled 19-Jul-2026 (per Apurva — "not very useful"). Code intact, not deleted.
Weekly trend reportMondays09:00 IST30 3 * * 1 Weekly Jira/support trend report to CEO Live
WhatsApp keep-aliveEvery 2 days18:00 IST30 12 */2 * * Pings the Twilio sandbox so the 72h WhatsApp session doesn't expire Live

Mira Updated 18-Sep-2026 — new LogiCloud jobs; Devang/Harshad routines still decommissioned

Sends as Mira@webxpress.in. Underlying skill is customer-project-tracker (Daily Brief/Scorecard/ETA Chaser) plus the mira skill.

⚠️ Updated 11-Sep-2026: Apurva intentionally removed both of Mira's Cowork Routines — the Devang Mail Autopilot (confirmed live 08-Aug-2026) and a previously-undocumented Harshad routine (never captured in this repo before removal — detail pending). Mira currently has no confirmed closed-loop automation at all. The Daily Brief / Scorecard / ETA Chaser rows below were already NOT in Cowork's Routines list before this — those times remain back-calculated from live email timestamps, not a confirmed schedule config.
JobCadenceIST timeUTC cronWhat it doesStatus
ABLBL LSP EDD/POD chaser newWeekly, Mondays10:00 IST0 10 * * 1 (server clock IST) Reads Control Tower for ABLBL: shipments past EDD and still undelivered, plus delivered shipments with no POD. Builds one Excel per logistics partner and mails it as Mira, with a consolidated summary to the project team. Recipients come from a reviewed LSP contact workbook on the server; EDD falls back to booking + lane TAT where the system EDD is missing or invalid Live on the Hawkeye server (cron, not Cowork)
Preview mode — all mail to project team + Apurva until contacts are signed off (target live 28-Sep-2026)
ABLBL Weekly LogiCloud Order-Health Digest new to this pageWeekly, Mondays11:00 IST30 5 * * 1 LSP-wise ageing of undelivered orders, orders booked with no EDD, and delivered-without-POD counts for ABLBL — the report that led to the chaser above Confirmed Cowork scheduled task — no human review
ABLBL LSP chaser (Mac-based version)Weekly, Mondays10:00 IST30 4 * * 1 First version of the chaser, run through Apurva's Mac because only that machine could reach the database. Replaced by the server cron job above Deleted 18-Sep-2026 — moved to the server, no laptop needed
Devang Mail AutopilotMon–Fri, twice daily14:00 & 21:00 IST30 8,15 * * 1-5 Reads Devang's mail, acts per Workflow 5, sends as Mira with no draft/approval step — was genuinely closed-loop Removed 11-Sep-2026 by Apurva
Harshad routineUnconfirmedUnconfirmedunconfirmed Never documented here before removal — pending detail from Apurva on what it did and since when Removed 11-Sep-2026 by Apurva
Daily Project BriefDaily~05:30–05:40 ISTunconfirmed Escalations, today's meetings, stuck items, PM-silence alerts, Jira fires, wins, Apurva's To Dos Active, mechanism unconfirmed
Weekly PM ScorecardMondays~05:32 ISTunconfirmed PM productivity RAG by cohort (Senior/Core), xlsx attached, to Apurva + Nehal only Active, mechanism unconfirmed
Jira ETA ChaserEvent-drivenMon–Fri scan, 10:00–19:00 ISTunconfirmed Emails the engineer when a new Jira epic/story opens — ticket table, open questions, deadline Active, mechanism unconfirmed
Escalation nudgesMon–Fri10:00–19:00 IST windowunconfirmed Auto-nudge if ETA missed or a ticket goes silent >48h Active, mechanism unconfirmed

Sharon Confirmed Cowork Routines — found 08-Aug-2026, previously undocumented

Campaign sends are still gated on Apurva's approval by design. But two recurring jobs run and send with zero human review — a correction to the earlier "no confirmed cadence" note on this page.

JobCadenceIST timeUTC cronWhat it doesStatus
Daily Sales BriefDaily08:30 IST0 3 * * * Scans Outlook + calendar for prospect activity, reads the Google Sheets pipeline tracker, flags stale/overdue items, lists today's sales meetings Confirmed Cowork Routine — no human review
11-Sep run took ~97min vs usual few — watch for repeat
Weekly Marketing DigestMondays08:00 IST30 2 * * 1 Campaigns sent that week, Brevo stats (opens/clicks/unsubscribes), recommendations Confirmed Cowork Routine — no human review
Campaign send loopOn-demand, per brief—n/a Brief → draft HTML email → Apurva approval → Brevo send → stats Human-gated, not scheduled
⚠️ Daily Sales Brief went dark for 17 days in July 2026 (silent failure, no fallback) before a Microsoft Graph fallback path was added for when Brevo credit hits 0. Worth watching if it ever goes quiet again.

Sharon — Sales Funnel Sync Droplet crontab, NOT a Cowork Routine — this is "sales lead sync"

Found by reading crontab -l directly on the droplet — invisible to list_triggers because it isn't Cowork-hosted at all.

JobCadenceIST timeUTC cronWhat it doesStatus
Sales Funnel SyncDaily07:00 IST30 1 * * * Matches Apurva's mail to open deals in Postgres marketing.deals, writes safe updates directly (never changes stage, never deletes, never creates a deal from cold mail), flags uncertain cases as a To Do, always sends a digest Confirmed — first real run expected next cycle (added 08-Aug-2026, no log yet)
⚠️ This writes directly to a database — the only job in this fleet that does. Its data store (marketing.deals) and the Daily Sales Brief's Google Sheets tracker are confirmed genuinely separate, unreconciled systems of record for the same pipeline.

Hawkeye production server hawkeye.webxpress.ai — new host in the fleet as of 17-Sep-2026

Control Tower's own box (Ubuntu 24.04, Postgres 16, PM2 apps). It now runs an agent job as well as its own housekeeping. Server clock is IST, so these crons are written in IST, not UTC.

JobCadenceIST timeCronWhat it doesStatus
LSP EDD/POD chaserWeekly, Mondays10:00 IST0 10 * * 1 See the Mira section — runs as its own service user, reads the database over localhost, mails through Microsoft Graph as Mira, and emails Apurva if a run fails Live — preview mode
Chaser output retentionWeekly, Mondays10:30 IST30 10 * * 1 Deletes generated Excel files older than 90 days Live
Hawkeye health checkTwice daily07:00 & 19:00 IST30 1,13 * * * Platform health-check runner (Hawkeye's own, not an agent) Live
Retention cleanupHourly—0 * * * * Hawkeye data retention job Live
Auto-heal (data only)Twice daily08:00 & 20:00 IST30 2,14 * * * Hawkeye's own repair pass over data inconsistencies Live
Health watchdogEvery minute—* * * * * Restarts the app if it stops responding Live
⚠️ A read-only review of this server on 17-Sep-2026 found its Postgres, Redis and app ports open to the internet, database logins accepted from any IP, and all services running as root — raised as Jira SOC-128 with Harshad. Worth closing before more agent jobs land here.

Velocity reporting 139.59.24.166 — claude-runner crontab, found 18-Sep-2026, previously undocumented

Nine cron lines under a second user on the same droplet. They belong to no registered agent and had never appeared on this page — found the same way "sales lead sync" was, by reading crontab -l.

JobCadenceIST timeUTC cronWhat it doesStatus
Velocity incremental refresh~13 times a dayspread through the daymultiple lines Refreshes Velocity report data for the reporting plugin Live, unowned
Sales Register MOR compactDaily03:00 IST30 21 * * * Builds the compacted Sales Register month-on-month dataset (company 10272) Live, unowned
Backstop re-export (+ retry)Daily, twice03:30 & 05:00 IST0 22 * * * / 30 23 * * * Re-exports anything the incremental refresh missed, with a later retry pass Live, unowned

Other droplet jobs 139.59.24.166 root crontab — infrastructure, no agent attribution

JobCadenceIST timeUTC cronWhat it doesStatus
Jira dashboard weekly report senderDaily check10:30 IST0 5 * * *Sends the Jira dashboard's weekly reportLive
Monthly customer reportsMonthly11:30 IST on the 5th0 6 5 * *Customer report pack generation (plus two dated one-off lines)Live
Supabase keep-aliveWeekly, Sundays06:00 IST30 0 * * 0Pings Supabase so the free project is not pausedLive
Stale session cleanupEvery 4 hours—0 */4 * * *Clears stale runner sessions on the dropletLive

Baldev No cron — production status itself unconfirmed

Nothing to schedule until it's confirmed whether hawkeye-codeagent is actually deployed and calling/messaging anyone.

JobCadenceStatus
Event-triggered chase (proposed)Real-time, on HawkEye eventNot confirmed live

Unowned infra monitoring Confirmed Cowork Routine — no agent attribution

Found 08-Aug-2026 while cross-checking the live Routines list. Doesn't fit any of the 4 registered agents.

JobCadenceIST timeUTC cronWhat it doesStatus
DO Server Health CheckDaily09:07 IST37 3 * * * External + internal health check on the WebXpressTMS droplet (139.59.24.166) serving www.webxpress.ai / sitestaging.webxpress.ai — response time, TTFB, /VERSION check Live, unowned — assign to Sara or a new entry
✅ Resolved — "sales lead sync" was Sales Funnel Sync, a droplet crontab entry (see the Sharon section above) — not a Cowork Routine, which is why the initial pass through list_triggers missed it. Lesson: always check a droplet's own crontab -l directly, not just the Cowork Routines API, when auditing an agent that might be droplet-hosted.
⚠️ 18-Sep-2026 re-check: the scheduled-task list now holds 5 live jobs — Sharon's two, the DO Server Health Check, the ABLBL Weekly LogiCloud Order-Health Digest (new here, see Mira) and a Hawkeye Manifest daily Jira refresh (weekdays 18:45 IST, Control Tower housekeeping rather than one of these agents). The Mac-based LSP chaser was deleted once the job moved to the Hawkeye server. Two new sources were read this round: the claude-runner crontab on the droplet (9 Velocity jobs, nobody's) and the Hawkeye server's own crontab.

⚠️ 11-Sep-2026 re-check: list_triggers now returns only 4 Routines total — Sharon's two (unchanged), the DO Server Health Check (unchanged), and a new unrelated "Hawkeye Manifest" job (Control Tower/Jira dashboard sync — not one of these 4 agents, out of scope here). Mira's Devang Mail Autopilot and a previously-undocumented Harshad routine are both gone — intentionally removed by Apurva. See the Mira section above.

Apurva's personal automations Cowork scheduled tasks — separate from the 4 agents above

Not part of the agent registry (no name/persona), but the same class of recurring automation — listed here for completeness since this page is meant to be the one place with every cron/schedule.

JobCadenceIST timeWhat it doesStatus
Daily task briefDaily07:00 IST Reads the Master Task Tracker + scans Outlook for new actionable email, emails a consolidated brief Active — Cowork scheduled task
WhatsApp task intakeEvery 30 min07:00–23:00 IST Polls Twilio for texted tasks, appends to the tracker, confirms on WhatsApp Active — Cowork scheduled task