Requestor get agreement and start activity, then activity expires but final invoice is never accepted and payment never happens #3126
Comments
averias
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During the last 3 days, Requestor 0x6c9d01fcdb18c8Dd91F901580fEaCB4b2E24B4c7 started an activity for 2-3 hours by consuming all resources of my machine and reached the expiration date time of the agreement. When that happened, the invoice was generated but the requestor never accepted that invoice so the payment was never done. While the activity was executed, Debit Notes were accepted every time the cost was updated
For me, it's strange that this issue happens since in my understanding ya-payments should manage this situation, it's also strange since only happened with the same requestor, other requestors which consumed task expiration time, accepted the invoices and paid
Is that a bug? Is there any way of blocking this requestor or any advise to avoid this situation? otherwise, I'll stop using Golem network until the issue is solved.
Some logs from the last issue today:
Proposal + agreement + task creation. Debit notes are issued every 2 minutes and accepted by Node 0xe5e94b0634ebe16fe961183180a5280764b2b7b2
Last cost updating and final cost calculated, agreement is broken because of expiration time, the invoice is sent but never accepted
The text was updated successfully, but these errors were encountered: