How It Works
- Write your code in a notebook cell as usual
- Click the clock icon on the cell toolbar (or right-click ā "Schedule")
- Pick a schedule ā every hour, daily, weekly, or custom cron expression
- Done. Alph runs the cell on schedule using your project's cloud compute
Each run is logged with its output, execution time, and status. You can view the full history in the cell's run log.
Note: Scheduled runs execute code inside your project ā they can read/write files, call APIs, update databases, and modify state within your project environment. The notebook itself isn't changed; you'd still publish any notebook content updates separately.
Example: Daily Data Report
Schedule the cell below to run every morning at 8am. It fetches data and generates a summary.
š Daily Report ā 2026-03-19 New users: 77 Active notebooks: 454 Compute hours: 320.0h API calls: 18,401
Example: Data Refresh Pipeline
Keep a dataset up to date by scheduling a refresh. This pattern works for any API or database.
Exchange rates as of 2026-03-19 12:22 USD ā EUR: 0.8713 USD ā GBP: 0.7529 USD ā JPY: 159.25 USD ā CAD: 1.3725
Example: Health Check / Monitoring
Use a scheduled cell as a lightweight uptime monitor.
Service Health Check ================================================== [OK] https://httpbin.org/status/200 ā 200 (671ms) [OK] https://httpbin.org/delay/1 ā 200 (1287ms) [OK] https://httpbin.org/status/200 ā 200 (264ms)
Cron Expressions
For custom schedules, use standard cron syntax:
| Expression | Schedule |
|---|---|
0 8 * * * | Every day at 8:00 AM |
0 */6 * * * | Every 6 hours |
*/15 * * * * | Every 15 minutes |
0 9 * * 1 | Every Monday at 9:00 AM |
0 0 1 * * | First day of every month |
āāāāāāāāāāāāāā minute (0-59)
ā āāāāāāāāāāāāāā hour (0-23)
ā ā āāāāāāāāāāāāāā day of month (1-31)
ā ā ā āāāāāāāāāāāāāā month (1-12)
ā ā ā ā āāāāāāāāāāāāāā day of week (0-6, Sun=0)
ā ā ā ā ā
* * * * *
Run History & Logs
Every scheduled run is recorded. Click the clock icon on a scheduled cell to see:
- Run history ā timestamp, duration, status (success/failure)
- Output ā the full output from each run
- Errors ā stack traces if something went wrong
You can also pause and resume schedules without deleting them.
Common Patterns
| Pattern | Schedule | Example |
|---|---|---|
| Daily report | 0 8 * * * | Fetch metrics, generate summary |
| Data refresh | 0 */6 * * * | Pull latest data from API/DB |
| Health check | */15 * * * * | Ping endpoints, alert on failure |
| Weekly digest | 0 9 * * 1 | Aggregate weekly stats |
| Model retrain | 0 2 * * 0 | Retrain ML model on new data |
| Cleanup | 0 3 1 * * | Archive old files, rotate logs |
No infrastructure to manage. No Docker. No Airflow. Just write a cell and schedule it.