Use this decision tree
| Current state | Best default | Reason |
|---|---|---|
| Low health, no recovery, important new loot | Withdraw | Preserve a productive run instead of gambling on one more node. |
| Stable squad, mission objective ready, next tier prepared | Finish | Convert preparation into progression. |
| You lack a specific current-area input and fights remain controlled | Farm briefly | Targeted repetition can close a known production gap. |
| Runs are easy but rewards no longer upgrade anything | Finish | Comfort without useful returns is a progression stall. |
| Next sector already overwhelms the squad | Short preparation runs | Improve equipment, supplies, and soldiers before another decisive push. |
What completion can change
Launch-week players report that completing an expedition advances area strength and equipment tiers. Those details are valuable but not yet an official numeric table. Record the current public build, difficulty, completed node, before/after Hazard Index, and reward quality before turning the observation into a rule.
The 30–40 minute target
In the August 10 developer AMA, the developer described roughly 30–40 minutes as a target expedition length—not a hard timer or an instruction to stay that long. You can save during an expedition, and pacing depends on route, difficulty, fights, and exploration.
Avoid the two common traps
- Fear of finishing: farming a solved area forever can delay the resources and blueprints only later areas provide.
- Automatic finishing: completing as soon as the button appears can advance difficulty before the base can replace ammunition, healing, armor, or soldiers.
Sources checked
- Official expedition overview ↗
- Developer expedition/save answers ↗
- Launch-week finish-versus-farm discussion ↗
Accessed August 13, 2026. External links open the original source.