# Publishing, scheduling and expiry

URL: https://kywi-docs-production.up.railway.app/authoring/publishing-scheduling-and-expiry
Type: docPage

Published At and Expires At fire on a sweep, every minute by default; Expires At can email people; Unpublish At hides a page; Feature Start/End time a callout.

The Publishing tab has five date fields. Published At, Unpublish At and Expires At govern whether a page is live, hidden or gone. Feature Start and Feature End, shown when Feature In Section is Scheduled, only control where a page is called out inside a section.

## Published At waits for the next sweep, not the clock

A page with a future Published At goes live when a background sweep notices the time has passed, not at the exact minute, and only if the page is Approved. The same field is also stamped automatically the first time a page goes live by any route, so on an already-published page it records when that happened rather than a dial you’re still turning.

## Choosing Published with a future date schedules the page

Setting Status to Published with a Published At still in the future saves the page as Approved and leaves it for the sweep, which publishes it at that time. The note under Status says “Saving schedules this to publish on <date>” before you save and “Scheduled for <date>” afterwards. The sweep keeps the date you set as the page’s publish date, and a page that is already published stays published if you move its date forward.

## Unpublish At hides a page without unpublishing it

Unpublish At doesn’t change a page’s status at all — the page stays published in the database. Visitors stop seeing it the moment the date passes, because every public read checks the date.

## Hidden pages stay listed in the admin

The Site Tree, and the Content List for editors and above, keep listing a page past its Unpublish At with a “Hidden since <date>” badge.

## Expires At moves a page to Archived — on the same delay

Expires At uses the same sweep: once the time passes, the page moves from published to Archived — not deleted. Unlike Unpublish At, nothing hides an expired page in the meantime, so it can stay live for up to one sweep interval (a minute by default) past its Expires At.

## Expiration Notify: tell people when a page expires

Under Expires At, Expiration Notify lets you pick who should hear about it: search the people with access to this site by name or email, add as many as you like, and remove anyone with a click. The picker stays disabled until Expires At is set. Changing the list takes editor or above; an author sees it but cannot change it.

When the time passes, each person you chose gets one email, whether the page was live, a draft or already archived — it is a prompt to review the page. Changing or clearing Expires At, including by restoring an older version, starts the notices over for everyone on the list; adding a person later notifies only that person. A copy or translation keeps the list but not what was already sent.

Someone who has since been deactivated, lost access to the site, or cannot read this page under its permissions is skipped, and the skip is recorded in the audit log. A failed send is retried with a growing delay, up to five attempts; in rare cases someone gets the notice twice.

## Notices need the sweep and a real email provider

Notices go out from the same sweep that archives the page, so where the sweep isn’t running nobody is emailed. They also need a real email provider — SMTP or one your host app supplies. With only the console logger configured, notices stay pending rather than being lost, and go out on the next sweep after a provider is added.

## Feature Start and Feature End: a callout window, not a schedule

Feature In Section has three settings. **Yes** features the page until you change it. **Scheduled** reveals Feature Start and Feature End, and the page counts as featured from the start up to, but not including, the end; leave one side blank for an open-ended window; both blank is the same as Yes. An end at or before the start cannot be saved. Switching back to No or Yes hides the dates without discarding them.

This is worked out when the page is read, not by the sweep, so a window opens and closes on time even where nothing is running the sweep.

## Featuring never makes a hidden page visible

A page that is unpublished, or outside its Unpublish At, is not shown whether it is featured or not.

## Published At and Expires At depend on the sweep running

Published At and Expires At are handled by one recurring background job, which also publishes [scheduled changesets](/governing/scheduling-a-changeset/). A Kywi site runs it every 60 seconds by default, unless whoever operates it turned it off — usually to run it from an external scheduler instead (see [Deploying a host app](/operating/deploying-a-host-app/#nothing-sweeps-unless-you-make-it-sweep)). It works only on Postgres: on MySQL, Published At, Expires At and Expiration Notify never fire. If a scheduled page hasn’t gone live a couple of minutes after its time, or an expired one is still showing, ask whoever operates the site whether the sweep is running. Unpublish At and the Feature window are checked on every read, so they don’t depend on it.
