Cronjob Catalog
This section contains the documentation for Logidav cronjobs, organized by risk level and alphabetically.
:::info Source of truth
The system crontab (system-crontab) is the source of truth for schedules. Documentation is generated by tools/cronjob_doc_generator.py.
:::
Statistics
| Metric | Value |
|---|---|
| Active cron entries | 164 |
| Unique commands | 115 |
| Code-linked commands | 95/115 (82%) |
| Critical commands | 46 |
| High priority commands | 40 |
Browse by risk level
Critical (46 commands)
Commands involving sales, payments, refunds, or stock mutations:
- Sales commands — order processing, status updates
- Payment commands — payment verification, refunds
- Refund commands — refund processing and validation
- Stock commands — inventory updates, stock synchronization
High priority (40 commands)
Commands with significant business impact:
- Product commands — synchronization, pricing, availability
- Sync commands — synchronization with external systems
- Import/Export — bulk data operations
Full catalog
Risk level definitions
| Level | Description | Impact | Examples |
|---|---|---|---|
| Critical | Sales, payments, refunds, stock | Immediate financial/inventory impact | menzzo:v2:sales:payment |
| High | Products, sync, orders, imports | Significant operational impact | menzzo:v2:products |
| Medium | Logs, stats, alerts, notifications | Support functions | menzzo:statistic |
| Unknown | Requires assessment | Not yet determined | Various |
Regenerate the documentation
python3 tools/cronjob_doc_generator.py
This will:
- Parse
docs/system-crontab.mdfor all active cron entries - Extract unique Symfony commands
- Generate documentation files in
docs/cronjobs/ - Attempt to locate corresponding Command classes
- Generate the coverage report
Key principles
- The crontab is the source of truth —
system-crontab.mdis the authoritative definition - Regenerate, don't edit — always regenerate base documentation from the source
- Risk first — prioritize documenting critical workflows