[ERR] NTFNS: Error fetching L402: no_route

[Dominion5254]

Expected behavior
Logs shouldn't have error [ERR] NTFNS: Error fetching L402: no_route.

Actual behavior
Logs are spamming the below errors/warnings. These failed payments don't seem to relate to my LND node - are these harmless? LiT seems to otherwise be working as expected.

2024-10-30T09:57:31-06:00  2024-10-30 15:57:31.917 [INF] L402: Payment of L402 token is required, resuming/tracking previous payment from pending L402 token
2024-10-30T09:57:31-06:00  2024-10-30 15:57:31.919 [INF] L402: Retrying payment of L402 token invoice
2024-10-30T09:57:32-06:00  2024-10-30 15:57:32.328 [WRN] LNDC: Payment 2f3ca0a0115c33f658138f200bb776ce74ddf0938439e2f6d942c6ece72243d2 failed: no_route
2024-10-30T09:57:32-06:00  2024-10-30 15:57:32.329 [ERR] NTFNS: Error fetching L402: no_route
2024-10-30T09:57:41-06:00  2024-10-30 15:57:41.867 [INF] LITD: Handling static file request: /
2024-10-30T09:57:57-06:00  2024-10-30 15:57:57.245 [INF] LITD: Handling static file request: /
2024-10-30T09:58:07-06:00  2024-10-30 15:58:07.399 [INF] L402: Payment of L402 token is required, resuming/tracking previous payment from pending L402 token
2024-10-30T09:58:07-06:00  2024-10-30 15:58:07.401 [INF] L402: Retrying payment of L402 token invoice
2024-10-30T09:58:08-06:00  2024-10-30 15:58:08.058 [WRN] LNDC: Payment c41771eadf4189a59be8c7d0baac726f60c4c74f25c3c933aad12c9d6576fcfc failed: no_route
2024-10-30T09:58:08-06:00  2024-10-30 15:58:08.058 [ERR] NTFNS: Error fetching L402: no_route

To reproduce
Fresh install of LiT 0.13.6-alpha

System information
LiT is running on StartOS 0.3.5~1
LiT is running with remote LND node
LiT 0.13.6-alpha pulled from dockerhub

[sputn1ck]

Hi,

the logs are harmless. A fix will be out soon to remove the logs spam.

[Dominion5254]

Thanks, does that mean there is an imminent 0.13.7-alpha?

[sputn1ck]

As the fix is only for log spam, it will only be included in the next release

[levmi]

It will be included in next litd release, but that will likely come later on (not this week), since the impact is only log spam, which is fairly harmless.