---
title: Release challenges in waves
description: Publish challenges hidden, release them on a schedule, lock a broken one, and chain them with prerequisites.
---

Dropping all challenges at once isn't the only way to run an event. A challenge moves through a fixed lifecycle: **draft → hidden → shown**, with **locked** as the emergency lever. Athena gives you three tools to stage it: **scheduled releases** that put a challenge on the board at a set time, **lock** for pulling a live challenge out of play, and **prerequisites** that unlock challenges as players solve others. Releases and locking live on the challenge's own page under **Lifecycle**; prerequisites are part of the editor. Drafts sit alongside published challenges on the Challenges page.

## The lifecycle

| Status | What players see |
| --- | --- |
| **Draft** | Nothing. It isn't a challenge yet, just saved authoring work. |
| **Hidden** | Nothing. Published and fully validated, waiting for you to release it. |
| **Scheduled** | Nothing yet. It appears by itself once the release time passes. |
| **Shown** | On the board and solvable. |
| **Locked** | On the board and readable, but no instances, hints, downloads or submissions. |

The one rule that shapes everything else: **once players have seen a challenge you cannot un-see it.** A challenge that has been live even for a moment can never go back to hidden; [lock it](#lock-a-broken-challenge) or [delete it](#delete-a-challenge) instead.

## Publish, then release

Publishing a draft produces a **hidden** challenge: fully validated, off the board. Releasing it is a second, deliberate step, so publishing can never surprise you by putting half-checked work in front of players.

Open the challenge and use the **Lifecycle** section:

- **Release immediately**: the challenge goes live when you press **Show challenge**.
- **Release at a specific time**: pick a date, then an hour and minute from the two selects beside it, and press **Schedule release**.
- **Release after CTF start**: enter a number of hours after the event's start time, then press **Schedule release**. Unavailable until the event has a start time.

A scheduled challenge shows as **Scheduled** in the challenges list with its release time, and appears by itself when the time passes. There is nothing to do mid-event.

:::note[Release times are in UTC]
The **Release at a specific time** picker is in UTC. A **UTC** label sits next to the hour and minute, and the *"Releases …"* confirmation line ends in **UTC**, with the same instant in your local time on the line beneath it, so you can check it without converting by hand. The challenges list shows the release in your local time too.
:::

An hours-after-start offset is saved as the resolved absolute time; reopening the page later displays it under **Release at a specific time**. That makes **Release after CTF start** handy for waves: "24 hours after start" needs no date math.

While a challenge is still **Scheduled** you can change your mind freely: press **Update release** for a new time, or **Unschedule** to return it to the hidden pool. Both stop being available the moment the release fires, because from then on players have seen it.

## Lock a broken challenge

**Lock** is the mid-event emergency lever for a challenge that is already live. Locking:

- terminates every running instance of the challenge immediately,
- refuses new instances, hint unlocks, file downloads and flag submissions,
- leaves the challenge on the board with its description readable, so players can see it exists and isn't solvable right now.

Use it when a challenge is broken or you suspect an instance is being abused. **Unlock** puts it back in play, but it does not restore the instances that were terminated, so players who had one need to start a new one.

Locking is recorded in your event's audit log along with the reason you type (audit logs are available on Pro and Enterprise).

## Delete a challenge

Deleting is the other way out of the lifecycle, and unlike locking it is permanent. **Delete** sits on the challenge's own page. It removes every solve, submission, hint unlock, instance, attached file and writeup for that challenge, and **reverses the points it moved**: each team that solved it loses what it earned, each team that bought one of its hints gets that cost back, and the net lands on the team's total straight away.

Before you confirm, the dialog shows exactly what is at stake for this challenge:

- how many **teams are affected** and the **net point movement** across them,
- how many **instances are still running**,
- how many **files and writeups** will be deleted from storage,
- and, if any challenges are gated behind this one, two separate lists: the ones that **unlock for every team immediately**, because this was their only prerequisite, and the ones that merely **lose one gate** and stay locked behind the prerequisites they have left.

Read the first of those two lists twice. Prerequisites are all-or-nothing: a challenge gated behind two others stays gated while the second one stands. Deleting a prerequisite therefore opens only the challenges it was the last gate for. But it opens those mid-event, for the whole field, with no further confirmation.

Running instances are terminated as part of the delete. If any of them can't be shut down, the delete is refused as a whole; nothing is removed, and the dashboard tells you the instances could not be terminated. Try again shortly.

:::note[Prefer lock while the event is live]
For a challenge that is merely broken, **lock** is almost always the right lever: it takes the challenge out of play without touching anyone's score, and you can undo it. Reach for delete when the challenge should never have existed. The score reversal is visible to players as their totals move, and there is no undo.
:::

## Chain challenges with prerequisites

The **Prerequisites** section of the editor gates a challenge behind others: pick challenges one at a time from the dropdown, and remove one with the ✕ next to its name. Each add and remove saves on its own. Players must solve every prerequisite before the challenge unlocks for them.

Two things to keep in mind:

- Only published challenges can be prerequisites; drafts can't, so publish a chain in order.
- Circular chains are rejected. If you set A to require B while B already requires A, the add fails and the error traces the loop it found as a chain of challenge IDs. Pick a different prerequisite.

Prerequisites are checked **per team**: the challenge unlocks for a team once that team has solved every prerequisite, so a teammate's solve unlocks it for everyone on the roster.

## Stage work in drafts

Unfinished challenges live as drafts on the **Challenges** page, marked with a **Draft** status; players never see them. Start one from **Add challenge** and click **Save as Draft**, which stores your progress as-is with no validation, so half-finished work saves fine. Click a draft's row to pick it back up; untitled work shows as *Untitled challenge*.

In the draft editor your edits autosave as you go, and **Publish Challenge** runs full validation. On success the draft becomes a **hidden** challenge, ready for you to release.

## Putting it together

A wave-based event, start to finish:

1. Before the event, author every challenge as a draft and finish them at your own pace.
2. Publish each one; they all land hidden, so nothing leaks while you work.
3. Release wave one immediately, and schedule later waves at *N* hours after start.
4. For chained storylines, publish parts in order and set each part's predecessors as **Prerequisites**. The wave controls when a chain's head appears; prerequisites pace players through the rest.
5. If something breaks mid-event, **lock** the challenge. Fix it, then unlock.
