Routes Listing Crash & Premium Lapse Cleanup

Bug Fixes

Routes listing could crash on certain partnership data (FSC-4003)

The routes listing endpoint could fail with a server error when a partnership network contained routes belonging to a company that had since been removed. The endpoint now filters those routes out cleanly, so the page always loads even if upstream data is in an unexpected state.

This was a listing-only crash. No route data was lost or altered, and your own routes were always intact.

Premium subscription lapses left orphaned companies and routes (FSC-4003)

When a user's premium subscription lapsed, the system removed their extra companies but did not properly extract those companies from any partnership networks they belonged to. The result was a small number of "orphaned" companies whose routes still appeared in partnership networks even though the companies themselves were gone.

The lapse handling has been rewritten to leave partnerships cleanly: leadership is transferred where needed, partnerships are dissolved when the lapsing company was the sole lead, and the company is then removed in a way that preserves the existing restore-on-resubscribe behaviour. A one-off cleanup has also been applied to the small number of historical cases (10 companies, 252 routes) so the network state matches what users see in their account.

If you re-subscribe to premium, your previously-removed companies are still restored exactly as before.