PHPackages                             sunnysideup/schedulizer - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Queues & Workers](/categories/queues)
4. /
5. sunnysideup/schedulizer

ActiveSilverstripe-vendormodule[Queues & Workers](/categories/queues)

sunnysideup/schedulizer
=======================

A silverstripe module for organising stuff to happen at arbitrary times in the future, useful with QueuedJobs

4.0.0(2y ago)012BSD-3-ClausePHP

Since Jun 6Pushed 2mo agoCompare

[ Source](https://github.com/sunnysideup/silverstripe-schedulizer)[ Packagist](https://packagist.org/packages/sunnysideup/schedulizer)[ RSS](/packages/sunnysideup-schedulizer/feed)WikiDiscussions main Synced today

READMEChangelogDependencies (1)Versions (14)Used By (0)

SilverStripe Schedulizer module
===============================

[](#silverstripe-schedulizer-module)

Fun module for organising stuff to happen at arbitrary times in the future.

Maintainer Contacts
-------------------

[](#maintainer-contacts)

- Stephen McMahon
- Marcus Nyeholt

Requirements
------------

[](#requirements)

- SilverStripe 3.1

Usage
-----

[](#usage)

- Create a Configured Schedule via the CMS admin
- From code, call
    - `ConfiguredSchedule::get()->filter('Title', $name)->first()->getNextScheduledDateTime();`

Configuring schedules
---------------------

[](#configuring-schedules)

For a job, schedules are read in particular precedence; first, the 'default' schedule is loaded. All other schedules are evaluated to see if they are applicable for the "current" time; if so, the desired schedule is substituted for, in increasing order of importance

- A ScheduleRangeDayType (ie weekday, Weekend)
- A ScheduleRangeDay (ie Monday, Tuesday)
- A ScheduleRange (ie specific date)

This allows configuration of a schedule set that is, for example

- Default - 6am - 6pm every day until 2020
- Weekends - 9am - 5pm
- Thursday - 6am - 9pm
- 25/12/2015 - 10am - 2pm

The decided upon schedule evaluates each in order, and selects that which is most specific.

**Create a schedule**

- Open `admin/schedulizer/`.
- Create a new schedule - for QueuedJobs usage, use the same name as the job classname
- Create a new Schedule Range; the first one should be called "Default" and have a type of "ScheduleRangeDefault". This is the baseline schedule that will be used
- Add additional schedules if needed
- Test the schedule by entering a date/time (YYYY-MM-DD hh:mm:ss format) and clicking "Test" - this will update with the next detected 'tick' time for that schedule.

**Modifying a schedule**

- Open `admin/schedulizer/`
- Select the schedule to modify
- On the "Schedule Ranges" tab, select the schedule to modify
- Modify the relevant fields
- Save and close, then test the new schedule as above.

License
-------

[](#license)

This module is licensed under the BSD license at

###  Health Score

37

—

LowBetter than 81% of packages

Maintenance55

Moderate activity, may be stable

Popularity5

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity70

Established project with proven stability

 Bus Factor1

Top contributor holds 96.3% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~399 days

Recently: every ~751 days

Total

10

Last Release

89d ago

Major Versions

1.0.0 → 2.0.02017-06-23

2.0.4 → 3.x-dev2020-10-04

3.0.0 → 4.0.02023-07-11

4.0.0 → 5.x-dev2026-04-06

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/167154?v=4)[Sunny Side Up](/maintainers/sunnysideup)[@sunnysideup](https://github.com/sunnysideup)

---

Top Contributors

[![sunnysideup](https://avatars.githubusercontent.com/u/167154?v=4)](https://github.com/sunnysideup "sunnysideup (26 commits)")[![nyeholt](https://avatars.githubusercontent.com/u/161730?v=4)](https://github.com/nyeholt "nyeholt (1 commits)")

---

Tags

silverstripeschedulecalendarqueuedjobscalculate days

### Embed Badge

![Health badge](/badges/sunnysideup-schedulizer/health.svg)

```
[![Health](https://phpackages.com/badges/sunnysideup-schedulizer/health.svg)](https://phpackages.com/packages/sunnysideup-schedulizer)
```

###  Alternatives

[symbiote/silverstripe-queuedjobs

A framework for defining and running background jobs in a queued manner

55892.3k102](/packages/symbiote-silverstripe-queuedjobs)[tarantool/queue

PHP bindings for Tarantool Queue.

65137.6k4](/packages/tarantool-queue)[okvpn/cron-bundle

Docker friendly Symfony cron bundle for handle scheduled tasks consistently, parallel or across a cluster, like Symfony Messenger

19506.0k1](/packages/okvpn-cron-bundle)[orisai/scheduler

Cron job scheduler - with locks, parallelism and more

4044.1k5](/packages/orisai-scheduler)[panlatent/schedule

Schedule plugin for CraftCMS

1034.8k](/packages/panlatent-schedule)[matviib/scheduler

Service for scheduling and managing cron tasks in laravel application

213.3k](/packages/matviib-scheduler)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)