Schedules

​

Overview

​

Technology Stack

​

How It Works

1. Create a function to run on schedule
2. Define a cron expression for the timing
3. Yboard registers the schedule with pg_cron
4. The function is invoked automatically at each interval

​

Execution Flow

1. pg_cron fires at the scheduled time
2. PostgreSQL trigger calls the function endpoint
3. Function executes with admin-level access
4. Results are logged for monitoring

​

Cron Expressions

┌───────── minute (0-59)
│ ┌───────── hour (0-23)
│ │ ┌───────── day of month (1-31)
│ │ │ ┌───────── month (1-12)
│ │ │ │ ┌───────── day of week (0-6, Sun=0)
│ │ │ │ │
* * * * *

​

Common Patterns

​

Secret Management

​

Best Practices

1. Keep schedules idempotent — Functions should be safe to re-run
2. Use appropriate intervals — Don’t schedule more frequently than needed
3. Add error handling — Log failures for debugging
4. Monitor execution — Check logs regularly for issues

​

Limitations

• Minimum interval is 1 minute
• Maximum execution time follows function limits (30 seconds)
• All times are in UTC