feat(proxy): cleanup spend logs cron verification, fix, and docs

[Harshit28j]

Relevant issues

Fixes #15081

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🆕 New Feature
📖 Documentation
✅ Test

Changes

• Feat: Enabled cron-based scheduling for spend log cleanup via maximum_spend_logs_cleanup_cron setting (e.g., "0 4 * * *").
• Docs: Updated docs/my-website/docs/proxy/spend_logs_deletion.md with configuration details and examples.
• Test: Added unit tests in tests/test_litellm/proxy/test_spend_log_cleanup.py to verify cron parsing and scheduler integration.
• Fix: Removed potential memory leak sources (jitter) from the cleanup job scheduling in proxy_server.py.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
litellm	Ready	Preview, Comment	Jan 14, 2026 2:18pm

[Harshit28j]