# Bug Reporting for v2.7.1

**URL:** <https://aurora4x.com/t/bug-reporting-for-v2-7-1/19>\
**Category:** Bug Reports\
**Created:** [February 23, 2026, 11:37pm UTC](https://aurora4x.com/t/bug-reporting-for-v2-7-1/19 "2026-02-23T23:37:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![AuroraSteve](https://yyz1.discourse-cdn.com/flex011/user_avatar/aurora4x.com/aurorasteve/32/96_2.png) [@AuroraSteve](https://aurora4x.com/u/AuroraSteve)\
**Post date:** [March 8, 2026, 1:33pm UTC](https://aurora4x.com/t/bug-reporting-for-v2-7-1/19/4 "2026-03-08T13:33:23Z")

</div>

> [@Kaiser](#):
>
> Hello, I got a 3418 error after a 5 days increment.

A weird one. #3418 is CargoLost. It happens when a ship is damaged or destroyed and cargo is lost. If it was a civilian, any contract is updated to account for the now missing item.

So if the ship picked up a mine to move, the supply and demand contracts would be updated to reflect that. If the ship is destroyed, the lost supply or demand is restored so another ship can fulfil the same contract.

That is done by updating an existing amount of demand, or re-instating a past one. There appears to be scope for a bug where the re-instatement is the opposite of a new order. So it tries to re-instate a supply order, but there is now a demand for the same thing. I’ve added some checks to prevent it, but this should be a very rare set of circumstances.

---

_[View the full topic](https://aurora4x.com/t/bug-reporting-for-v2-7-1/19)._