Sylvics Apply for the beta
Halden Flow exception codesReference
REFERENCE

Halden Flow exception codes

📌 TL;DR / Quick Summary <div style="background: rgba(0,0,0,0.3); border: 1px dashed rgba(255,255,255,0.2); padding: 15px; border-radius: 8px; color: rgba(255,255,255,0.7); margin-bottom: 30px;"> The 23 exception types Halden Flow recognises, and what makes each one fire. Fictional product, real headache. I wrote the table on 8 January because I had been saying exception for a year as if it were one thing (🔤 Exception, in freight), and Exception list queries would not run on a loose word. </div>

🛠️ Instructions / Core Material Grouped the way a dispatcher thinks about them, not the way the database stores them.

# Code Group Fires when
1 LATE-PU Late Pickup not confirmed 60 minutes after the booked slot
2 LATE-DL Late Delivery not confirmed 60 minutes after the booked slot
3 ETA-SLIP Late The carrier's estimate moves by more than two hours
4 MISS-CUT Late The shipment misses the terminal or depot cut-off
5 NO-SHOW Late The carrier does not turn up at all and says nothing
6 HOLD-CUS Held Customs holds the shipment
7 HOLD-DOC Held A required document is missing or rejected
8 HOLD-PAY Held Released only against a payment nobody has made
9 HOLD-TERM Held The terminal holds it for its own reasons
10 DMG Goods Damage reported at any scan
11 SHORT Goods Fewer pieces arrive than were booked
12 OVER Goods More pieces arrive than were booked
13 TEMP Goods A temperature reading leaves the agreed range
14 REFUSED Goods The consignee refuses the delivery
15 MISROUTE Routing A scan appears at a place that is not on the route
16 ADDR Routing The address cannot be found or is wrong
17 SPLIT Routing One shipment is travelling as two or more
18 ROLLED Routing Moved to a later sailing or departure
19 RETURN Routing On its way back to the sender
20 NO-SCAN Data No event at all for twelve hours while in transit
21 DUP Data The same booking exists twice
22 MISMATCH Data Weight or dimensions differ from the booking by more than 10 percent
23 POD-MISS Data Delivered, but no proof of delivery after 24 hours

The five Late codes are most of every list I have ever counted. NO-SCAN is the one dispatchers fear, because silence is the only exception that does not announce itself.

⚠️ Key Warnings / Constraints

  • A code is not a cause. LATE-DL says the lorry was late. It does not say whether the lorry, the gate or the booking was at fault.
  • One shipment can carry several codes at once. Count shipments or count exceptions, and say which. I got this wrong in the first draft of the pilot numbers.
  • The thresholds (60 minutes, two hours, twelve hours) are defaults. Kestrel has changed two of them, so their list is not comparable with anyone else's without checking.
  • After 20 March auto-triage groups by these codes. If a code is ever added, the rules in 📂 Exceptions Inbox general availability need a line for it the same day.

🔗 Related Entities & Resources