Scheduled promotes

Promote a tested version at a set time, for an event or a sale, and put things back automatically when it ends.

A weekend event, a sale, a seasonal theme: test the config in staging now, and schedule the promote to production for when it starts. With an end time, production goes back to what it served before when the event ends, so nobody has to be awake for it.

terminal
$ hotcfg promote game-config --from staging --to production \
    --at 2026-11-21T18:00:00Z --revert-at 2026-11-24T06:00:00Z
✓ Scheduled game-config staging v14 → production at 2026-11-21 19:00
  revert   production back to what it serves just before the promote, at 2026-11-24 07:00, unless it changes in between
  id       sch_4f1c2a9e7b30d851
  cancel   hotcfg schedules cancel game-config sch_4f1c2a9e7b30d851

In the dashboard, open the bin, press Promote…, tick Schedule it for later, and pick the times (in your own time zone). Waiting schedules are listed on the bin's Payload and History tabs, with Cancel.

What ships

The version that's current in the source now, here staging v14, not whatever staging serves when the time comes. You tested v14; v14 is what goes out, even if staging moves on in the meantime. When it runs, it's checked against the bin's schema again, like any promote.

It runs within about 15 seconds of its time, and reaches apps like any promote: the edge cache is purged, and webhooks send a promote event, credited to whoever scheduled it.

Putting it back

With an end time (--revert-at, or Then put production back at), production is rolled back to the version it served just before the promote, as a new version, like any rollback.

The revert only happens if production still serves what the schedule put there. If someone published, promoted or rolled back production during the event, that's someone's decision, and the schedule leaves it alone: the revert is skipped, and the schedule says why. It's also skipped if a progressive rollout is running then, or if production served nothing before the promote.

When a schedule can't run

A schedule is checked when you make it, and again when it runs. It fails, changing nothing, if by then:

  • whoever scheduled it can no longer change the target: they left the organization or are no longer an administrator (for production), or the API key was revoked or has expired;
  • the version is no longer kept (older versions are pruned by your plan's history limit);
  • the bin's schema changed and the version doesn't match it any more;
  • a progressive rollout is running in the target.

A failed schedule is marked in the dashboard's list, recorded in the audit log, and whoever scheduled it gets an email with the reason. Deleting an environment cancels the waiting promotes from or to it, and skips a waiting revert of it. Deleting the bin deletes its schedules.

Cancelling

Cancel in the dashboard, or:

terminal
hotcfg schedules list game-config
hotcfg schedules cancel game-config sch_4f1c2a9e7b30d851

Before the promote, cancelling drops the whole schedule. After it, it cancels only the revert: the promoted version stays.

Who can schedule

The same people who can promote into the target: for production, administrators and the owner, or a secret key allowed to write production. A limited key needs both environments. Times are checked against the server's clock, in UTC; the API takes them as RFC 3339 (2026-11-21T18:00:00Z, or with an offset, 2026-11-21T19:00:00+01:00), up to a year ahead.

Plans

On Free, one scheduled promote can wait at a time, counting one whose revert is still waiting. On Pro, up to 25 can wait at once. If an organization moves to Free, schedules already made still run; new ones are refused until none is waiting.

In the API

Add at, and optionally revert_at, to a promote:

terminal
curl -X POST "https://api.hotcfg.run/v1/acme/game-config/promote" \
  -H "Authorization: Bearer $HOTCFG_API_KEY" -H "Content-Type: application/json" \
  -d '{"from_env":"staging","to_env":"production","at":"2026-11-21T18:00:00Z","revert_at":"2026-11-24T06:00:00Z"}'

It answers 202 with the schedule. GET /v1/{org}/{bin}/schedules lists a bin's schedules, and DELETE /v1/{org}/{bin}/schedules/{id} cancels one. A schedule's state is pending, waiting_revert (promoted, revert to come), done, reverted, revert_skipped, failed or cancelled, with error saying why for the last ones.

Last updated 17 November 2026