Automatically support scheduled invalidation + staticStatuses/update-statuses

[timkelty]

As of 5.7.0, the staticStatuses config setting allows the use of the update-statuses CLI command to update element statuses as their publish or expiration date passes, which will trigger static caches to be invalidated.

Cloud users can create a scheduled command (currently 1hr is the minimum interval) that runs update-statuses, and static caches will be invalidated within the cron window (1hr).

Ideally, Cloud would support this natively without the need for a cron, by having Craft trigger a one-time scheduled command in the future.

staticStatuses/update-statuses: craftcms/cms#17024

[andrewfairlie]

Just to add some context to why this would be a game changer.

Some of our publishing sites use scheduled posts a lot, but using the standard Craft behaviour means that if the home or a category page is cached, the scheduled post simply wont show on the page which is a big 👎 but waiting an hour for it to go live is also not acceptable to them.

So we have very short (imo) cache times to try to get some caching even if it's only for a few minutes but if we could use static statuses, and have Craft Cloud do this each minute or so we could have longer lasting caches and really help the performance and availability of the sites.

[timkelty]

Totally agree! We're doing some feature planning for the the remainder of 2025, at which point we will update our roadmap and priorities. I think this would be a good one to bump up on the list.