Official recovery steps
The v1.0.3 hotfix fixed a bug where units on Expeditions could get stuck and never return.
For a save that already contains stuck units from before v1.0.3, the developer gave this recovery sequence:
- Update the game to v1.0.3 or newer.
- If Expeditions are running, let all of them finish.
- Do not auto-start new Expeditions while waiting.
- If no Expedition is running, start one Expedition.
- When the final quest/Expedition finishes, the stuck units should be recovered.
This page exists because the fix is more than “restart the game,” and older saves can carry the broken state forward until the recovery trigger runs.
If the units still do not return
Do not repeatedly recall units or spam new Expeditions. First confirm:
- the game reports v1.0.3 or later;
- no other Expedition is still active;
- auto-start is off while you run the recovery sequence;
- you allowed the final activity to finish normally.
If that sequence still fails, report it on the official Steam Discussions thread with your version and save context. There isn’t a verified save-file edit for this bug.
Is this still relevant in v1.0.6?
The underlying bug was fixed in v1.0.3. This page remains useful only for players carrying an affected older save forward. New saves on current versions should not need the recovery procedure for that specific bug.
Source
- Official v1.0.3 hotfix mirrored by SteamDB: steamdb.info/patchnotes/25140430/