Scheduled is a Python recurring job declaration specification provided by tiangolo/scheduled. Its goal is to describe recurring scheduled jobs in pyproject.toml with intuitive, minimal configuration. It is not a task scheduler runtime and does not provide a concrete execution implementation; instead, it defines how tasks should be declared and how Providers should read and run them.
Configuration lives under the tool.scheduled namespace. Each task is identified by a unique job-id and requires two fields: every and entrypoint. every supports minute, hour, day, week, and month to express run frequency, while entrypoint points to a Python callable using the importable.module:some_callable format. Compared with cron, it avoids less intuitive string syntax such as 0 0 *, making it better suited to common needs like βonce a dayβ or βonce a week.β
The documentation also emphasizes that a Provider can assign stable but distributed run times within a cadence. For example, a daily task could be assigned to run at 10:30, helping avoid resource spikes caused by many tasks running at midnight. Thanks to the standard TOML format, PyCharm or VS Code, together with extensions such as Tombi, can provide autocomplete and inline error hints.
The project source code is hosted on GitHub and uses the MIT License. No commercial pricing is mentioned in the main documentation. It is important to note that Scheduled itself is only a specification: it does not include a runner, hosted platform, monitoring, alerting, or queueing capabilities. Providers may even support only a subset of frequency values. As a result, ecosystem maturity and production reliability mainly depend on the implementation provider.
Its strengths are simplicity, readability, alignment with common Python project configuration practices, and helping platforms distribute task load more evenly. Its limitations are that it is much less expressive than cron and is not suitable for complex calendar rules, precise time control, or advanced scheduling scenarios. In failure cases, Providers should at least attempt to run a job once per cycle, and users also need to write idempotent tasks.
It is well suited for declaring simple recurring tasks in Python projects, and also for cloud platforms, PaaS products, or internal platforms that want to design a unified scheduling configuration. If you need complex cron expressions, a mature runtime, or task orchestration, you should continue using cron or a dedicated scheduling system.
The main documentation does not provide information about access from mainland China, mirrors, or payment options. Since the source code is hosted on GitHub, actual access may depend on the network environment. The specification itself is free and has no payment barrier.
β This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on scheduled.work official site.
scheduled.work is an Unknown Dev Tools provider. TG4G tracks its product information, an overall rating of 6.0/10, and a China-accessibility score of China direct-connect friendly. Click "Visit Official Site" to reach scheduled.work directly.