Sathira Sri Sathara
5158c52db5
- Introduced new endpoints for account overview, analytics, and metrics. - Implemented authorization matrix and backup/restore documentation. - Added smoke test script and updated package dependencies. - Created detailed production checklist and runbook for deployment. - Established cron operations and notification event matrix documentation. - Enhanced security and validation audits for analytics and metrics services. - Added unit tests for analytics and metrics functionalities.
12 lines
955 B
Markdown
12 lines
955 B
Markdown
# Cron Operations
|
|
|
|
| Job | Schedule | Authority / boundedness | Idempotency |
|
|
|---|---|---|---|
|
|
| Notification cleanup | configured source schedule | DB records; retention bounded | repeated delete safe |
|
|
| Inventory reservation expiry | frequent | batch-limited DB scan | reservation state/event key |
|
|
| Checkout expiry | frequent | batch-limited DB scan | checkout/reservation state |
|
|
| Loyalty reconciliation | scheduled | configured batch | ledger event IDs |
|
|
| Support SLA + recommendation retention | every 5 minutes | 100 SLA / 1,000 event max | deterministic escalation key / old-event deletion |
|
|
|
|
Cron starts only when the deployment enables `RUN_CRON`; use one dedicated scheduler replica. Current jobs use local `noOverlap` where available but do not all have a distributed lock, so multi-instance cron is prohibited until staging validates/implements Redis locking. All times are server/UTC clock time unless a domain snapshot says otherwise.
|