Cron Jobs
Define scheduled prompts in yourchucky.json configuration file. When you run chucky deploy, your cron jobs are synced to Chucky’s scheduler.
Configuration
Add acrons array to your chucky.json:
Cron Expression Format
Standard 5-field cron expressions:Examples
| Expression | Description |
|---|---|
0 9 * * * | Every day at 9:00 AM |
0 9 * * 1-5 | Weekdays at 9:00 AM |
*/15 * * * * | Every 15 minutes |
0 0 1 * * | First day of every month at midnight |
0 0 * * 0 | Every Sunday at midnight |
Full Schema
Deploying Crons
When you runchucky deploy, the CLI:
- Reads cron definitions from
chucky.json - Deletes any existing cron schedules for the project
- Creates fresh schedules for each enabled cron
Example Configurations
Daily Report with Slack Webhook
Weekly Metrics with Structured Output
Multiple Crons with Different Schedules
Callback Webhooks
Results are POSTed to your callback URL when the cron completes:HMAC Verification
If you provide asecret, the request includes an X-Chucky-Signature header:
Timezones
Use IANA timezone identifiers:| Timezone | Example Cities |
|---|---|
UTC | Default |
America/New_York | New York, Miami |
America/Los_Angeles | Los Angeles, Seattle |
Europe/London | London |
Europe/Paris | Paris, Berlin |
Asia/Tokyo | Tokyo |
Asia/Shanghai | Shanghai, Beijing |
Australia/Sydney | Sydney |
Best Practices
Set appropriate budgets
Set appropriate budgets
Always set
maxBudgetUsd to prevent runaway costs. Start low and increase based on actual usage.Use callbacks for production
Use callbacks for production
Don’t rely on polling. Configure webhooks to receive results immediately when crons complete.
Test with disabled crons
Test with disabled crons
Set
enabled: false while testing your configuration, then enable when ready.Use structured output for data pipelines
Use structured output for data pipelines
When feeding results into other systems, use
outputFormat to ensure consistent JSON structure.Viewing Cron Status
View your cron jobs in the Chucky Dashboard:- Next run time - When the cron will next execute
- Last run status - Success/failure of the most recent run
- Run history - Past executions with results
Concurrency
Cron jobs share the same concurrency limits as the Incubate API:| Tier | Concurrent Tasks |
|---|---|
| Hobby/Free | 2 |
| Starter | 5 |
| Pro | 10 |