Unknown node causing ThunderHub to crash when checking Forwards screen.

Describe the problem/bug Someone opened and after a few minutes closed a channel to my node. The closing transaction is here: https://mempool.space/tx/5f3fdca0dca3d6afea5aaf70cf751ad0c3e17bb6283eb2bc88d8039c3e638e98 The closing transaction Peer is listed as Unknown. Channel ID is 849168x3160x0 Peer ID is 03d5c6cb2ea6d8730c2a3334b106d38f56c6248fd270695122c00568a65856e967 Neither one is showing up on any Lightning explorers

If I go to the Home page of ThunderHub, the Routing report lists the node as "Node not found"

Issue is that now if I try to go to Forwards screen, ThunderHub just crashes to the login screen. It doesn't actually log me out, it just dumps to the login screen where I have to press the Connect button to get back to Home.

lncli forwarding history shows them as

        {
            "timestamp":  "1719153995",
            "chan_id_in":  "933670090142384128",
            "chan_id_out":  "933666791519354883",
            "amt_in":  "10466",
            "amt_out":  "10465",
            "fee":  "1",
            "fee_msat":  "1010",
            "amt_in_msat":  "10466090",
            "amt_out_msat":  "10465080",
            "timestamp_ns":  "1719153995708641331",
            "peer_alias_in":  "unable to lookup peer alias: edge not found",
            "peer_alias_out":  "Play-Asia.com"
        },
        {
            "timestamp":  "1719154053",
            "chan_id_in":  "933670090142384128",
            "chan_id_out":  "933666791519354890",
            "amt_in":  "45",
            "amt_out":  "44",
            "fee":  "1",
            "fee_msat":  "1000",
            "amt_in_msat":  "45418",
            "amt_out_msat":  "44418",
            "timestamp_ns":  "1719154053229807475",
            "peer_alias_in":  "unable to lookup peer alias: edge not found",
            "peer_alias_out":  "_LEGALIZE_MATH_"
        },
        {
            "timestamp":  "1719154087",
            "chan_id_in":  "933670090142384128",
            "chan_id_out":  "933666791519354883",
            "amt_in":  "102",
            "amt_out":  "102",
            "fee":  "0",
            "fee_msat":  "43",
            "amt_in_msat":  "102231",
            "amt_out_msat":  "102188",
            "timestamp_ns":  "1719154087648304491",
            "peer_alias_in":  "unable to lookup peer alias: edge not found",
            "peer_alias_out":  "Play-Asia.com"
        },

Your environment

Version of ThunderHub: 0.13.31
Deployment method: Start9 node

Expected behavior I expect to go to Routes and see all the routed transactions same as I see them on the Home screen.

EDIT:

Since it has been over 24 hours, I can go into the Forwards screen now without it crashing, because these transactions don't show up in 1D view. If I switch the display to List and increase the time to 7D, all the transactions including these Unknown ones show up fine. If I keep it on 7D display and switch to Graph, it crashes to the login screen again. The issue seems to be with the graph unable to show them in that particular screen.

apotdevin / thunderhub

Unknown node causing ThunderHub to crash when checking Forwards screen. #614