Blockheight disagreement, not aborting - WIRE_INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS

[JssDWt]

node id: 03226c467e77b102a718acd72e92a65830906c6de186c7ac07cdee021d30469089
session id: 7276342403923968

time="2024-12-21T22:07:59+01:00" level=info msg="BreezSDK: [INFO] node-logs: DEBUG   plugin-pay: cmd 34 partid 8: Blockheight disagreement, not aborting." group=lightning
time="2024-12-21T22:07:59+01:00" level=info msg="BreezSDK: [INFO] node-logs: INFO    plugin-pay: cmd 34 partid 8: failed: WIRE_INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS (reply from remote)" group=lightning

It appears there's a blockheight mismatch in a regular payment, where the greenlight node is behind. I believe the greenlight node uses the 'current' blockheight rather than the sync block height when sending payments? Why is this node behind?

[cdecker]

It does use the highest known chain length as offset. So either bitcoind is returning an old height (that'd be a new one), or we are using the correct height. Notice that the disagreement could also be on the recipient side (do you have access to verify on the recipient?) and/or the recipient could believe the invoice is expired due to clock drift or it has already been paid (which is the nice thing to do here, and not just claim multiple times).

I'll of course check the session to verify as soon as possible.