[Arkiv - beta tests report] Provider doesn't terminate Agreement when Requestor disappears after destroying activity

[nieznanysprawiciel]

Scenario:

• Provider and Requestor sign Agreement
• Activity starts, computations are done
• Requestor deamon destroys activity
• Immediately Requestor yagna daemon is killed, so the Provider is unable to send last DebitNote ([2025-10-29T17:07:46.844+0100 WARN ya_provider::payments::payments] Error sending debit note: Failed to send debit note [2d1ba611-f272-4927-bb50-20576b205059] for activity [57e3a9dc915042fcb2d571c5cbd635d7]. HTTP error requesting POST http://127.0.0.1:7465/payment-api/v1/debitNotes/2d1ba611-f272-4927-bb50-20576b205059/send: 500 Internal Server Error; msg: 'Service bus error: Remote service at /net/0x3333333330a671211031493f06be9483343a2d7a/payment/SendDebitNote error: Bad request: endpoint address not found' Retry in 13.424100084s. error must be triggered)

The result:

• Payment module is unable to finish the activity, because it retries it until succeeds
• Agreement is not terminated, because:
  • Activity was terminated correctly
  • Send DebitNote timeout is not active when we are processing last DebitNote, so the Provider-side termination won't be triggered
  • We never schedule a new expiration tracker for a next activity creation, because we never reached that point.

Logs:
Agreement: ddd98c91c5927d40263925cbebdd6a405f101a8f3a0f4d8aeec705870a4b28ef
Activity: 57e3a9dc915042fcb2d571c5cbd635d7

ya-provider_r2025-10-29_23-20-16.log