Troubleshooting orders and matches

An order was accepted but nothing happened#

Check its execution outcome. Admission only puts an order into the command stream. A later refusal can report changed ownership, a stale unit, insufficient stock, a busy producer or a missing prerequisite. An executed move may still be travelling or searching for a route.

A worker stopped adding resources#

Look for a carried load, a depleted source, an unreachable route or a lost suitable drop-off. Carried resources are not yet spendable stock. A queued order may still be waiting behind current work.

A caravan returned without payment#

Check whether the original market-access grant remained active, whether the home and destination survived, and whether the trip was retargeted. A new agreement cannot revive a trip invalidated earlier. A full stock capacity can also delay a valid whole payment; no partial payout is invented.

The map does not show an event#

Fog distinguishes current sight from remembered information. Public town ownership and signed agreements do not reveal private units, cargo or capture progress. An eliminated ruler's permitted partner view is also limited by that partner's knowledge.

For a file refusal, keep the message and verify its build matches the save or recording. See saves and replays before retrying.