Django Tasks Scheduler
Documentation can be found in https://django-tasks-scheduler.readthedocs.io/
Introduction Video
Watch this introduction video to learn about django-tasks-scheduler and its features.
Usage
- Update
settings.pyto include scheduler configuration:
import os
from typing import Dict
from scheduler.types import SchedulerConfiguration, Broker, QueueConfiguration
INSTALLED_APPS = [
# ...
"scheduler",
# ...
]
SCHEDULER_CONFIG = SchedulerConfiguration(
EXECUTIONS_IN_PAGE=20,
SCHEDULER_INTERVAL=10,
BROKER=Broker.REDIS,
CALLBACK_TIMEOUT=60, # Callback timeout in seconds (success/failure/stopped)
# Default values, can be overridden per task/job
DEFAULT_SUCCESS_TTL=10 * 60, # Time To Live (TTL) in seconds to keep successful job results
DEFAULT_FAILURE_TTL=365 * 24 * 60 * 60, # Time To Live (TTL) in seconds to keep job failure information
DEFAULT_JOB_TTL=10 * 60, # Time To Live (TTL) in seconds to keep job information
DEFAULT_JOB_TIMEOUT=5 * 60, # timeout (seconds) for a job
# General configuration values
DEFAULT_WORKER_TTL=10 * 60, # Time To Live (TTL) in seconds to keep worker information after last heartbeat
DEFAULT_MAINTENANCE_TASK_INTERVAL=10 * 60, # The interval to run maintenance tasks in seconds. 10 minutes.
DEFAULT_JOB_MONITORING_INTERVAL=30, # The interval to monitor jobs in seconds.
SCHEDULER_FALLBACK_PERIOD_SECS=120, # Period (secs) to wait before requiring to reacquire locks
)
SCHEDULER_QUEUES: Dict[str, QueueConfiguration] = {
"default": QueueConfiguration(URL="redis://localhost:6379/0"),
}
- Update
urls.pyto include scheduler urls:
from django.urls import path, include
urlpatterns = [
# ...
path("scheduler/", include("scheduler.urls")),
]
- Run migrations:
python manage.py migrate
- Check out the admin views:
Local development environment
You can install pre-commit hook in the repo to add it as a git hook by
running: pre-commit install. It is configured to check all change files based on configuration in
.pre-commit-config.yaml.
Sponsor
django-tasks-scheduler is developed for free.
You can support this project by becoming a sponsor using this link.
Contributing
Interested in contributing, providing suggestions, or submitting bugs? See guidelines at this link.
Metadata
Release files for django-tasks-scheduler 4.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_tasks_scheduler-4.4.0.tar.gz | 118.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_tasks_scheduler-4.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 301.4 kB
Release files / django_tasks_scheduler-4.4.0.tar.gz
| Download URL | django_tasks_scheduler-4.4.0.tar.gz |
|---|---|
| Size | 118.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14f75d1367714e9c288c9f1c37648273210cf8f85a34afd9973bf03f07ab275a
|
|
BLAKE2b-256 checksum How to use checksums |
58690f9df629f8c2fa70bf34f08684522da3f45389f80807fd0c7cd1afab1184
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logRelease files / django_tasks_scheduler-4.4.0-py3-none-any.whl
| Download URL | django_tasks_scheduler-4.4.0-py3-none-any.whl |
|---|---|
| Size | 182.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
214a3feb10d8285c9ad595bed97245fdbf6723ca7775372673439d62c49a5c0b
|
|
BLAKE2b-256 checksum How to use checksums |
f9ed469b82ab2e307a8a4fb50bbbb6174d04ab0ed896f435d4fe759f4bcee7f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency log