Drupal is a registered trademark of Dries Buytaert
cms 2.1.3 — Update released for Drupal core (2.1.3)! drupal 10.5.11 — Update released for Drupal core (10.5.11)! drupal 11.3.11 — Update released for Drupal core (11.3.11)! drupal 11.2.13 — Update released for Drupal core (11.2.13)! drupal 10.6.10 — Update released for Drupal core (10.6.10)! cms 2.1.2 — Update released for Drupal core (2.1.2)! drupal 11.1.10 — Update released for Drupal core (11.1.10)! drupal 10.5.10 — Update released for Drupal core (10.5.10)! drupal 10.4.10 — Update released for Drupal core (10.4.10)! drupal 11.2.12 — Update released for Drupal core (11.2.12)! drupal 11.3.10 — Update released for Drupal core (11.3.10)! drupal 10.6.9 — Update released for Drupal core (10.6.9)! drupal 10.6.8 — Update released for Drupal core (10.6.8)! drupal 11.3.9 — Update released for Drupal core (11.3.9)! drupal 11.3.8 — Update released for Drupal core (11.3.8)! drupal 11.3.7 — Update released for Drupal core (11.3.7)! drupal 11.2.11 — Update released for Drupal core (11.2.11)! drupal 10.6.7 — Update released for Drupal core (10.6.7)! drupal 10.5.9 — Update released for Drupal core (10.5.9)! cms 2.1.1 — Update released for Drupal core (2.1.1)!
← All modules

scheduled_transitions

3,204 sites Security covered
View on drupal.org

Users may select a specific revision, and it will be changed to a different moderation state at a specified date.

Scheduled Transition differentiates from other scheduling projects by providing a smooth user experience, and by not adding scheduling metadata as fields on the scheduled entity.

The module works with any entity type compatible with content moderation (nodes, custom blocks, etc). No custom integration work required. Transitions may be scheduled for individual translations of each entity.

Documentation

A guide to installation, config, and usage is available in the Introduction to Scheduled Transitions blog post.

Minor configuration and permissions are required to set up the module. Site builder and user guide are available in the Guide to Scheduled Transitions.

Introduction Video

Usage

The following example uses a flow of draft to published, but any transition is possible. The general flow for users is:

  1. Users create content as normal, creating revisions naturally. Revisions move between states such as draft, needs review, published.
  2. When the content reaches a point where its ready to be published. Find the ready revision and take note of which revision it is.
  3. Go to the Scheduled transitions tab for the content.
  4. Click Add scheduled transition button.
  5. Locate the ready revision, and schedule it.

Versions

Version 2.6 2.7 2.8 2.9 Drupal core ^10.2 ^10.3 || ^11 ^11.1 ^11.3 || ^12 PHP Compatibility >=8.2 >=8.3 >=8.3 >=8.5 Stability Stable Stable Stable N/A Support Bug fixes only Bug fixes only Bug fixes only New features and bug fixes Until PHP 8.2 security support ends or Drupal 10 series EOL, whichever is earlier. Until PHP 8.3 security support ends or Drupal 10 series EOL, whichever is earlier. Until PHP 8.3 security support ends or Drupal 11 series EOL, whichever is earlier. Until PHP 8.5 security support ends or Drupal 11 series EOL, whichever is earlier.

View support for previous versions.

Installation and dependencies

Scheduled transitions is currently only compatible with Content Moderation workflows

Activity

Total releases
9
First release
Jul 2025
Latest release
4 days ago
Release cadence
39 days
Stability
44% stable

Release Timeline

Releases

Version Type Release date
2.9.0-beta4 Pre-release May 29, 2026
2.9.0-beta3 Pre-release May 28, 2026
2.9.0-beta2 Pre-release May 28, 2026
2.9.0-beta1 Pre-release May 28, 2026
2.8.4 Stable Mar 13, 2026
2.9.x-dev Dev Mar 11, 2026
2.8.3 Stable Jul 29, 2025
2.8.2 Stable Jul 29, 2025
2.8.1 Stable Jul 23, 2025