Schedule in the time zone you use
Set a five-field cron expression and time zone. The console previews upcoming occurrences so you can check the schedule before saving it.
Cron jobs
Set the schedule.
Get on with your day.
Run recurring application tasks with a cron expression and your chosen time zone. Use the code you already have, then follow each execution in the console.
Your code. Infrastructure included.
0 8 * * *Every day · 08:00 UTC
daily-summary / scheduled task
MONsend_daily_summary Complete
TUEsend_daily_summary Complete
Your scheduleFive-field cron expressions
Your time zoneReview upcoming run times
Run historyStatus and output for each execution
CRON JOBS ON OPENSTEAD
Recurring work, without a server crontab.
Keep scheduled commands with the application they belong to. Configure the schedule, review upcoming runs and inspect the result of each execution.
Run your application command
Execute a management command, script or container command using the built application and its configured environment.
Know how a run ended
Review execution status, start and finish times, output and errors. Trigger a manual run when you want to test a change or perform the work now.
MADE FOR YOUR STACK
Run on your calendar, with your application context.
Scheduled jobs use your application build and service configuration. A named time zone makes the schedule easier to understand than translating every local time by hand.
- Preview the next scheduled occurrences in the console.
- Trigger a manual execution without changing the recurring schedule.
- Configure a timeout of up to 12 hours for a cron run.
A daily application summaryopenstead / configuration
SCHEDULE CONFIGURATIONCommand python manage.py send_daily_summary
Schedule 0 8 * * *
Time zone Africa/Lagos
Timeout 600 seconds
Runs every day at 08:00
in the selected time zone.Make recurring commands safe to retry. A schedule does not provide exactly-once execution of external side effects.
PUT IT TO WORK
Built for the work
your application does.
Daily summaries
Prepare scheduled reports and recurring messages using the data in your application.
Data synchronization
Fetch changes from an external API or move records between systems at a regular interval.
Application housekeeping
Clean up expired records, refresh cached data or reconcile application state on a schedule.
HOW IT WORKS
A command, a calendar and a clear result.
Choose the command
Connect the repository or container image that contains your scheduled task. Set the command and required environment variables.
Set the schedule
Enter the cron expression, choose a time zone and check the next run times. Set an execution timeout suited to the task.
Test and monitor
Deploy the job and trigger a manual run. Use execution history and logs to check subsequent scheduled runs.
Can I choose a time zone?
Yes. Configure the time zone alongside a standard five-field cron expression. Openstead shows upcoming execution times so you can check the resulting schedule.
Can I run the task immediately?
Yes. Once the cron service is deployed, use a manual run to execute its configured command and inspect the result in run history.
How is a cron job different from a worker?
A cron job starts work according to a schedule. A background worker runs a process that typically waits for and consumes jobs from a queue. Choose the service that matches how the work is triggered.
What happens if a task runs too long?
The run has a configurable timeout, up to 12 hours. Set a limit suited to the workload and design the command to handle interruption and subsequent execution safely.
MAKE YOUR NEXT MOVE
Make recurring work one less thing to remember.
Your code. Infrastructure included.