Specbee: How to automate content publishing with the Drupal Scheduler module?

Scheduler has an actively maintained release that supports both Drupal 10 and Drupal 11. Check the module’s project page on drupal.org for the latest compatibility details before installing on a new major version.
Editors draft content in advance and set it to go live at a precise moment. Until that time arrives, the content stays unpublished and invisible to site visitors.
Admin > Content > Scheduled lists every node currently queued for publishing or unpublishing. It’s the single view for editors to manage and review the full schedule.
Drupal publishes or unpublishes the content automatically once the scheduled time is reached, as long as cron is running.

• With over 50,000 active installs, the Drupal Scheduler module is one of the most widely adopted content management modules on drupal.org. It is compatible with Drupal 10 and Drupal 11.
• The Drupal Scheduler module lets editors set exact publish and unpublish dates for any node or taxonomy term – no manual status changes required.
• Scheduling is configured per content type, so it appears only where your team needs it.
• Scheduler integrates with Drupal’s content moderation system, fitting seamlessly into approval-based editorial workflows.
• Publishing and unpublishing are processed on the next cron cycle, not at the exact scheduled second. Shorter cron intervals mean tighter timing.
• Lightweight Cron is available for smaller sites without a server-level cron job.

What are the use cases of the Drupal Scheduler module?

The Drupal Scheduler module automates content publishing and unpublishing by letting editors set exact dates and times on any node or taxonomy term, no manual status changes required. 
No one has to be online when the publish window opens.
To schedule a specific piece of content:

• Blog posts at a specific date and time: Without Scheduler, someone has to be online and ready to hit publish at the right moment — a dependency that breaks at weekends and across time zones.
• Marketing campaign launches: A summer sale page that goes live a day late misses its window. Scheduler eliminates that risk without any developer involvement at publish time.
• Event announcements: Event pages that outlive their date confuse visitors and damage search results. Scheduler takes the page down automatically.
• Time-sensitive promotions: A job posting that stays up past its application deadline creates real operational problems. Unpublish scheduling handles it.
• Seasonal content across time zones: Teams managing content for international audiences use Scheduler to set publish times in advance and eliminate the coordination overhead.

How does the Drupal Scheduler module work?

Schedule content to publish automatically

A straightforward example of how that looks in practice:
Timing matters more than most editors expect. A summer sale page that goes live a day late misses its window. A job posting that stays up past the application deadline creates real problems downstream. Manually tracking publish dates across a busy CMS is where mistakes happen.

Schedule content to unpublish automatically

After saving, Drupal displays a confirmation notice with the scheduled date and time. To review everything queued across the site, go to Admin > Content > Scheduled.
Go to Administration > Structure > Content types and edit the content type you want to configure.

Configure scheduling per content type

If your site manages campaigns, events, or time-sensitive content across time zones, Scheduler is a low-overhead addition that pays for itself in the first campaign cycle. Start with the content types your team updates most frequently, configure cron to run every 5 to 15 minutes, and the editorial burden of manual publish timing effectively disappears. 

Under the Scheduler section, two options appear:

Fit scheduler into your editorial workflow

Scheduler also supports Lightweight Cron, which triggers processing via site visitor traffic when a configured interval has elapsed. It’s a practical option for smaller sites without a server-level cron job.

1. Create draft
2. Review and approve
3. Schedule for publishing
4. Scheduler publishes at the defined time

If cron runs every hour, content scheduled for 10:00 AM might go live at 10:05 or 10:55, depending on when the last run happened. For sites where timing precision matters, a shorter cron interval is worth the configuration effort.

How to install and configure the Drupal Scheduler module?

Your site stays current without anyone manually archiving content after the fact.
You can enable both or just one. Once you save, additional configuration settings appear within the same Scheduler section.
Out of the box, Scheduler works with nodes and taxonomy terms. Support for media entities depends on the version and any additional contributed modules. Check the Scheduler project page on drupal.org and the Scheduler Media module for current compatibility details.
Scheduler lets editors define exact dates and times for content to be published or unpublished automatically. Instead of manually flipping a node’s publication status -a change to the underlying content record that controls whether it’s visible to site visitors  – you enter a timestamp and move on.
Scheduler is applied selectively, one content type at a time. Editors only see scheduling options for the types where it’s been enabled.
This keeps the editing interface clean and limits scheduling to content that actually needs it.

How to enable scheduling for a specific content type?

Install the module using Composer:
Disabling the Scheduler module will stop all scheduled publishing and unpublishing from processing. The scheduled date data stored on content nodes is not automatically deleted, but no actions will fire until the module is re-enabled. Scheduled content that was supposed to go live in the interim will remain in its previous state until Scheduler runs again.

• Publishing – lets editors schedule when content goes live automatically
• Unpublishing – lets editors schedule when content comes down automatically

drush en scheduler -y

How can you schedule a node in Drupal?

Scheduler works alongside Drupal’s content moderation and workflow systems. For teams with an approval process, the content lifecycle becomes:

1. Go to Administration > Content
2. Edit the content item
3. Find the Scheduling options section
4. Enter your Publish on and/or Unpublish on date and time
5. Save

composer require drupal/scheduler
After installation, enable it via Drush – Drupal’s command-line tool for managing modules and configuration:  

Does the Drupal Scheduler module depend on Cron?

If you need help configuring Scheduler or integrating it with an editorial workflow, talk to the Specbee team.
Key Takeaways:
The module works with both content and taxonomy. Taxonomy terms are the categorization labels Drupal uses to organize content, such as tags and content categories. 

Final thoughts

Scheduler uses Drupal’s configured site time zone for processing. For international sites, it’s worth setting a consistent reference time zone in Drupal’s Regional and Language settings and communicating that to editors. Content scheduled in the admin interface follows that site-level time zone, not the editor’s local time.
Lightweight Cron triggers Scheduler’s processing via site visitor traffic when a configured time interval has elapsed. It’s built for smaller sites that don’t have access to a server-level cron job.
The Drupal Scheduler module removes the dependency on someone being at the keyboard at the right moment. Editors set a date and time. Drupal handles the rest. Unlike manual publishing or custom cron scripts, Scheduler requires no developer intervention after initial setup and works within Drupal’s existing editorial interface.  

Frequently Asked Questions

What is the Drupal Scheduler module? 

Here are the common use cases and what can go wrong without Scheduler:

Can I enable scheduling for some content types and not others? 

You can also enable it through the Drupal admin interface at Administration > Extend.

Does Scheduler integrate with Drupal content moderation workflows? 

Yes, and this is worth getting right before you deploy. Cron is a time-based job scheduler that Drupal uses to run background tasks, like processing publish queues, at configured intervals. Scheduler relies on Drupal’s cron system to process publish and unpublish tasks. When the scheduled time arrives, the action does not fire immediately. It fires on the next cron cycle.

What happens if cron isn’t running when content is scheduled to publish? 

It does. Scheduler works alongside Drupal’s built-in content moderation system. Content follows your existing approval workflow and is then scheduled for automatic publishing once it reaches the approved state.

What is Lightweight Cron in the Scheduler module? 

Once enabled, go to Administration > Configuration > Content Authoring > Scheduler to configure it. From there, set date and time formats, enable scheduling for specific content types, and define default scheduling behavior.

Where can I see all scheduled content in one place? 

Content that needs to go live or expire at a specific time is a routine operational need. Scheduler handles it without workarounds or manual tracking. For teams managing campaigns, events, or time-sensitive content in Drupal, it’s one of those modules that quietly earns its place.

Is the Scheduler module compatible with Drupal 10 and Drupal 11? 

Content can also be set to come down automatically. Event pages after the event ends, job postings past their application deadline, promotional banners after a campaign closes, temporary announcements – Scheduler handles all of them.

Can Scheduler handle time zone differences for international sites? 

Yes. Scheduler is configured per content type. You can turn on publishing only, unpublishing only, or both for each type independently. Content types where scheduling is not enabled are unaffected.

What happens to scheduled content if I disable the Scheduler module? 

The content stays unpublished until the next cron run. Scheduler doesn’t trigger publishing directly; it depends on cron to process its queue. Running cron every 5 to 15 minutes keeps the gap between scheduled time and actual publish time small.

Does Scheduler work with media entities or only nodes?

Scheduler is a Drupal module with over 50,000 active installs that automates content publishing and unpublishing. Editors set specific dates and times on any node or taxonomy term, and Drupal handles the status change automatically, no manual intervention needed.