Terminal Repair and Reset Progress
The safe order for starting a Terminal repair before Reset, with current timer and transition rules.

Table of contents
Once a Terminal's repair countdown has actually started, that repair progress persists through System Reset. Items submitted before the countdown starts do not persist. The safe dividing line is therefore the visible running repair, not the first material contribution.
This behavior was introduced in v1.0.3. Current Terminal repair times are dynamic rather than one universal six-hour value.
Use this order before a reset
- Open the Terminal requirement. Read the current items, resources, and state from the live repair panel.
- Gather the complete requirement. Do not rely on a partial submission surviving a reset.
- Submit until repair begins. The important state change is the active countdown or progress indicator.
- Verify that time is moving. A filled requirement and a running repair are different states.
- Only then compare System Reset. If you reset, return to the Terminal and confirm the already-started progress remains.
- Let the final seconds finish. Current protection prevents System Reset when a Terminal is less than ten seconds from completion.
Why an old repair can still show six hours
v1.0.3 replaced the fixed six-hour Terminal repair with dynamic times and made the first Terminal significantly faster. A repair already in progress in a save created before that change can keep its old time. The corrected timing applies when the next Terminal begins.
That makes the version and start time more useful than comparing your timer with another player's current run. Do not restart a save merely because one legacy countdown is longer.
Terminal, Reactor, and Spire are separate checks

The current repair protections do not make every infrastructure target behave identically:
- Terminal: submitted items are not retained across Reset, but an active repair countdown is retained.
- Terminal completion: a Reset is blocked during the final ten seconds to avoid a transition conflict.
- Reactor Auto Repair: as of v1.0.5, map automation waits for the Reactor repair to finish before checking energy or Biomass and deciding to leave.
- Spires and Reactors: their permanent-progress purpose is covered in the infrastructure guide; this page does not claim the same timer or material rule for all three target types.
If the repair still looks stuck
Check the visible state in this order:
- current game version;
- whether all required items were submitted;
- whether a countdown actually started;
- whether the save began that repair before v1.0.3;
- whether the machine is inside the final protected seconds;
- whether the symptom is a Map route problem rather than the repair itself.
Avoid save editing, deleting the body grid, or repeatedly resetting as a first response. Record the Terminal state and version before closing or changing the run. Use the Map automation guide if Auto Explore or Auto Repair is choosing the wrong destination, and review System Reset and Augments before spending the resulting permanent points.
Related guides
System Reset and Augments Explained
Understand what System Reset is for, how permanent Augments shape later runs, and what to verify before confirming a reset.
Read guideWhat Reactors and Spires Do
Learn why Reactors and Spires matter to the prestige loop and why their demo behavior can be misleading.
Read guideAuto Explore and Auto Repair Guide
Configure Auto Explore and Auto Repair, verify resource leave conditions, and diagnose current map automation symptoms through v1.0.6.
Read guideMap, POIs, Terminals, and Survivor Groups
Unlock travel, choose useful points of interest, repair infrastructure, and understand the four survivor-group goals.
Read guideIDLE_DIRECTIVE Updates and Patch Notes
Review the player-facing changes in IDLE_DIRECTIVE v1.0.2 through v1.0.6, including maps, repairs, saves, items, and progression.
Read guide