Django management command monitoring is easy to overlook. A command works when you run it manually: python manage.py sync_invoices Enter fullscreen mode Exit fullscreen mode So you put it in cron, Celery beat, systemd, Kubernetes, or a platform scheduler. Then one day it stops running. The app is still online. Uptime checks are green. But invoices are missing, reminder emails are not sent, reports are stale, and nobody notices until the data is already wrong. The problem Django management commands often run outside the normal request/response path. They are commonly used for: billing reconciliation scheduled emails CRM or payment provider syncs CSV imports cleanup jobs search index rebuilds report generation expired trial handling These jobs usually run through something outside Django: 0 2 * * * cd /srv/app && /srv/app/venv/bin/python manage.py sync_invoices Enter fullscreen mode Exit fullscreen mode That creates a monitoring gap.…