Advanced Python Scheduler (APScheduler) is a Python library that lets you schedule your Python code to be executed later, either just once or periodically. You can add new jobs or remove old ones on the fly as you please. If you store your jobs in a database, they will also survive scheduler restarts and maintain their state. When the scheduler is restarted, it will then run all the jobs it should have run while it was offline [1].
Among other things, APScheduler can be used as a cross-platform, application specific replacement to platform specific schedulers, such as the cron daemon or the Windows task scheduler. Please note, however, that APScheduler is not a daemon or service itself, nor does it come with any command line tools. It is primarily meant to be run inside existing applications. That said, APScheduler does provide some building blocks for you to build a scheduler service or to run a dedicated scheduler process.
APScheduler has three built-in scheduling systems you can use:
Cron-style scheduling (with optional start/end times)
Interval-based execution (runs jobs on even intervals, with optional start/end times)
One-off delayed execution (runs jobs once, on a set date/time)
You can mix and match scheduling systems and the backends where the jobs are stored any way you like. Supported backends for storing jobs include:
APScheduler also integrates with several common Python frameworks, like:
There are third party solutions for integrating APScheduler with other frameworks:
Documentation
Documentation can be found here.
Source
The source can be browsed at Github.
Reporting bugs
A bug tracker is provided by Github.
Getting help
If you have problems or other questions, you can either:
Ask in the apscheduler room on Gitter
Ask on the APScheduler GitHub discussion forum, or
Ask on StackOverflow and tag your question with the apscheduler tag
Release files for APScheduler 3.11.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| apscheduler-3.11.3.tar.gz | 110.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apscheduler-3.11.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 176.3 kB
Release files / apscheduler-3.11.3.tar.gz
| Download URL | apscheduler-3.11.3.tar.gz |
|---|---|
| Size | 110.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd2fcc9330039a81a5893472ad49facf23a6d5604cbe1d918c835c6de7834d5a
|
|
BLAKE2b-256 checksum How to use checksums |
8c6beeff360196bb20b312c9e762a820fd1b2c6d809466c755ef57863478e454
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 28, 2026.
Transparency logRelease files / apscheduler-3.11.3-py3-none-any.whl
| Download URL | apscheduler-3.11.3-py3-none-any.whl |
|---|---|
| Size | 66.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bbeb2ec02d23d3c06a6c07ed7f0f3939ada6680eb121fae809a69bb42c537a30
|
|
BLAKE2b-256 checksum How to use checksums |
42c98638db32514dbb9157b3d82680c6faea89283523edf9ed2415ea3884f2ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 28, 2026.
Transparency log