Technical notes on web development, DevOps, and AI integration.
1 article
Two parity assertions showed a past scheduled_at publishing instantly and a future event_date only setting sort order.
TL;DR: A parity test showed a past scheduled_at gets published instantly in the POST response, so there's no cron worker; treat published as derived from the current time. A future event_date still publishes immediately, proving it only controls sort order, not visibility. Keep both fields separate and trust the admin response for effective status.