Handle invoice exception in purchase does not work

Before creating an issue, I’d rather ask here first.
In Tryton 6.8

  1. create purchase
  2. process invoice
  3. cancel invoice
  4. execute ‘Handle Invoice Exception’ wizard with all purchase lines
  5. a new invoice is generated, but the purchase invoice state is still ‘Exception’
  6. execute ‘Handle Invoice Exception’ wizard again, an empty list appears

I have not found a way to get rid of the exception. Tested on two independent docker instances.

In Sale the exception handling works fine.

Then report a bug: https://bugs.tryton.org/

Here it is: Handle invoice exception in purchase does not work (#12476) · Issues · Tryton / Tryton · GitLab

(post deleted by author)

Updated my install to most recent versions, but still have this issue. Are patches incorporated into these versions ?

tryton==6.8.3
trytond==6.8.4
trytond-account==6.8.3
trytond-account-invoice==6.8.2
trytond-account-invoice-correction==6.8.0
trytond-account-invoice-line-standalone==6.8.0
trytond-account-invoice-stock==6.8.1
trytond-account-payment==6.8.0
trytond-account-product==6.8.0
trytond-account-statement==6.8.0
trytond-account-stock-continental==6.8.0
trytond-bank==6.8.0
trytond-carrier==6.8.0
trytond-commission==6.8.1
trytond-company==6.8.0
trytond-company-work-time==6.8.0
trytond-country==6.8.0
trytond-currency==6.8.1
trytond-party==6.8.1
trytond-product==6.8.0
trytond-product-price-list==6.8.0
trytond-project==6.8.0
trytond-project-invoice==6.8.0
trytond-project-revenue==6.8.0
trytond-purchase==6.8.3
trytond-purchase-amendment==6.8.0
trytond-purchase-history==6.8.0
trytond-purchase-request==6.8.0
trytond-purchase-secondary-unit==6.8.0
trytond-sale==6.8.2
trytond-sale-amendment==6.8.0
trytond-sale-history==6.8.0
trytond-sale-invoice-grouping==6.8.0
trytond-sale-price-list==6.8.0
trytond-sale-secondary-unit==6.8.0
trytond-sale-shipment-grouping==6.8.0
trytond-sale-stock-quantity==6.8.0
trytond-sale-supply==6.8.2
trytond-stock==6.8.3
trytond-stock-consignment==6.8.0
trytond-stock-forecast==6.8.0
trytond-stock-secondary-unit==6.8.1
trytond-stock-supply==6.8.0
trytond-timesheet==6.8.0
trytond-timesheet-cost==6.8.0
trytond-web-shop==6.8.0
trytond-web-user==6.8.0

Or could the problem be that the exception already occurred in July 23? - How then would I handle it?

Cheers,
Wolf

Hi Wolf,
I updated the code manually some weeks ago and it worked with past invoice exceptions without any problem. So I guess it is not in the latest release.
Maxim