Axiomancer
Changelog

April 24, 2026

Cell scoring writes restored, more reliable Equasis vessel enrichment, restored daily risk-scoring features, and fewer port-call timeouts.

April 24, 2026LocusFix

Cell scoring writes restored

Fixed an issue where the cell scoring pipeline reported successful runs while silently writing zero rows. Upsert errors were being swallowed rather than surfaced, so score updates had been stalled since around April 22. Scoring now fails loudly on write errors and persists updates correctly — cell scores, rankings, and downstream queries through the Locus API are flowing again. No action is required on your part.

April 24, 2026OverwatchFix

More reliable Equasis vessel enrichment

Fixed an issue where vessel metadata enrichment from Equasis was timing out intermittently under load, causing roughly 120 failed enrichment requests per day since April 19. The underlying enrichment relay now handles concurrent requests instead of queueing them serially, so registered owner, flag state, and deadweight tonnage fields populate more consistently — especially during overlapping enrichment runs. No action is required on your part.

April 24, 2026OverwatchFix

Restored daily risk-scoring feature generation

Fixed an issue where the daily job that prepares training features for the vessel risk score model had been failing every night since April 20 due to a column mismatch introduced in a prior migration. The job now runs cleanly, so risk-model features — including ship-to-ship transfer history and identity-change events — stay current. No action is required on your part.

April 24, 2026OverwatchFix

Fewer timeouts in port-call and disruption processing

The vessel-visits processor previously ran out of memory when handling large batches of port events, and the disruptions pipeline could hit its 150-second wall-clock limit when any single GDELT query was slow to respond. The visits processor now uses smaller batches, and each disruption query enforces its own 15-second timeout so a single slow response no longer blocks the full run. Port-call timelines and disruption signals stay current through load spikes. No action is required on your part.

On this page