ShippedScheduled jobs
Give recurring work its own schedule and runtime. Keep routine application tasks out of the web process.
Turn a command into a recurring task
Define the application command that should run, the schedule it should follow, and the environment it belongs to. Use a separate job for recurring exports, synchronization, or maintenance. That makes the work visible as an application resource instead of relying on a timer hidden inside a web process that may be replaced during deployment.
Make timing and overlap deliberate
Choose how the job should behave if an earlier run is still working, a run fails, or an execution takes too long. Plan around the schedule’s timezone and the task’s deadlines. Clear overlap and retry rules help you avoid duplicate reports, competing updates, or a growing backlog when a downstream service slows down.
Inspect the result of each run
Use execution status and logs to see whether the scheduled work completed and where it failed. Connect only the secrets and data resources the job needs. For work that modifies records or contacts an external service, record progress in durable storage so a later retry can continue safely instead of repeating every step.
A little more detail
Questions about Scheduled jobs?
Should I put a scheduler inside my web server?
Use a scheduled job when the task must run independently of web traffic and web deployments. An in-process timer can stop when its process is replaced and can run multiple times when the web service has multiple instances.
What happens if a job takes longer than its schedule interval?
Choose an overlap policy suitable for the task and set a realistic execution limit. A job that updates shared records may need serialized execution, while independent work may safely run concurrently.
Background workers
Run background workers on Shipped for queues, imports, notifications, and long-running application tasks, with separate resources and deployment history.
Explore Background workersLogs
Inspect Shipped build and application logs from the portal or your coding agent, with project and release context for deployment troubleshooting.
Explore LogsSecrets
Manage application secrets in Shipped, connect them to the right services and environments, and keep credentials out of Git and frontend bundles.
Explore Secrets
Django
Deploy Django apps with PostgreSQL, file storage, workers, and private configuration on Shipped. Keep your models, views, and admin.
Explore DjangoFrom your workspace to the web