Closing & reopening

Closing a launch freezes it. A closed launch can be reopened by anyone whose role holds the Launches — Close permission.

How to close

• The Close launch button in the launch header (red on hover).
• The project's auto-close policy (see below).

What happens on close

• The launch is marked closed.
• All write endpoints on the launch (and its results) refuse further mutations.
• The launch contributes to your project's dashboards.

Reopening

Use Reopen from the launch header (or the card menu on the Launches list). Reopening lifts the freeze — triage, defect links, and tag edits work again — and the launch goes back to contributing as an open run. Close and Reopen are both gated by the Launches — Close permission.

Auto-close policy

Project Settings → General → Launch auto-close policy has two independent settings:

• Auto-close finished launches after (hours) — closes launches once they've finished.
• Interrupt stuck IN_PROGRESS launches after (hours) — for a run still IN_PROGRESS past the limit, marks it interrupted and closes it, so a hung run doesn't stay open forever.

Both settings close (freeze) the launch; they differ only in the resulting execution state (finished vs interrupted). New projects start with both set to 1 hour. You can change or clear either at any time; existing projects keep whatever they were set to.