49 lines
1.5 KiB
Markdown
49 lines
1.5 KiB
Markdown
# Daily Digest - Failsafe Backup System
|
|
|
|
## Current Setup (Updated 2026-02-23)
|
|
|
|
**Cron Job:** Daily Digest - 7am CST
|
|
**Job ID:** `69fb35d3-f3be-4ed2-ade0-3ab77b4369a9`
|
|
**API Key:** `daily-digest-2026-secure-key` ✅ Fixed
|
|
**Timeout:** 5 minutes
|
|
**Notify on failure:** YES ✅
|
|
|
|
## Failsafe Mechanism
|
|
|
|
If the daily digest cron job fails:
|
|
|
|
1. **Auto-retry:** Up to 3 attempts with 30s delays
|
|
2. **User notification:** You will be notified of the failure
|
|
3. **Backup file:** Digest content saved to `memory/YYYY-MM-DD-digest-failed.md`
|
|
4. **Manual posting:** Can be posted manually via:
|
|
```bash
|
|
curl -X POST "https://blog-backup-two.vercel.app/api/digest" \
|
|
-H "Content-Type: application/json" \
|
|
-H "x-api-key: daily-digest-2026-secure-key" \
|
|
-d @memory/2026-02-23-digest-failed.json
|
|
```
|
|
|
|
## Last Successful Digest
|
|
- **Date:** 2026-02-23
|
|
- **Posted at:** 6:36 PM CST (manual fix)
|
|
- **Status:** ✅ Live on blog-backup
|
|
|
|
## Known Issues Fixed
|
|
- ✅ Wrong API key in cron job (was `cron_daily_digest_2025`, now `daily-digest-2026-secure-key`)
|
|
- ✅ Timeout extended to 5 minutes
|
|
- ✅ Notify on failure enabled
|
|
- ✅ Retry logic added
|
|
|
|
## Manual Digest Generation (Emergency)
|
|
If cron fails for multiple days:
|
|
1. Tell me "generate yesterday's digest"
|
|
2. I'll research and post manually
|
|
3. Or use the backup file saved in memory/
|
|
|
|
## Monitoring
|
|
- Check daily at 7:05 AM CST
|
|
- If no notification received = success
|
|
- If failure notification received = check backup file
|
|
|
|
---
|
|
*Last updated: 2026-02-23 18:37 CST* |