The flag does not by itself say the booking is wrong. It says the computed transport plan contains an internal inconsistency worth a human look. A tradeflow either has an anomaly or it does not, and the dashboard flags any tradeflow with an anomaly present.
To review it, open the tradeflow and look at the plan. Check the references: is more than one booking or BL riding on one tradeflow that should be separate? Is a container number reused from an earlier shipment? Check the ports: is a POL or final POD missing or mis-resolved, producing a circular or truncated plan?
The anomaly page lists API locations with empty dates, orphan events, and a container with no transport plan as possible triggers. If the input is correct and the plan is still inconsistent, report the case to support. Anomalies are about plan consistency, not timeliness.
Example
A booking has a port location supplied through API but no usable date. Dockflow flags the tradeflow. You open the tradeflow, check the references and ports, and see the plan is inconsistent. If the input is correct, you report the case to support.