Skip to main content

How It Works

Jobs are registered in a central registry and executed via three triggers:

Cron (HTTP) Vercel cron hits /api/cron/[job]
Scheduler setInterval in persistent containers
Manual Admin dashboard at /admin/jobs

Every execution is logged to PostgreSQL with status, duration, trigger type, and result count. The runJob() wrapper handles timing and fire-and-forget logging — if the DB insert fails, the job result is still returned.

Registered Jobs

session-cleanup registered
log-cleanup registered
notification-cleanup registered
telegram-token-cleanup registered
discord-token-refresh registered
analytics-cleanup registered
analytics-rollup registered

Recent Executions

JobStatusTriggerDurationResultTime
analytics-rollupsuccessscheduler747ms01d ago
telegram-token-cleanupsuccessscheduler2722ms01d ago
log-cleanupsuccessscheduler2723ms01d ago
analytics-cleanupsuccessscheduler770ms4111d ago
discord-token-refreshsuccessscheduler684ms01d ago
notification-cleanupsuccessscheduler688ms01d ago
session-cleanupsuccessscheduler684ms01d ago
analytics-rollupsuccessscheduler126ms02d ago
analytics-cleanupsuccessscheduler174ms1562d ago
discord-token-refreshsuccessscheduler502ms12d ago

Key Files

Registry src/lib/server/jobs/index.ts
Runner src/lib/server/jobs/runner.ts
Scheduler src/lib/server/jobs/scheduler.ts
Cron route src/routes/api/cron/[job]/+server.ts
Schema src/lib/server/db/schema/jobs/job-execution.ts
Admin src/routes/admin/jobs/+page.svelte