[Bug]: Notifications stay in "In progress" state

[Nuranto]

Description

Some notifications stays in "In progress" state. Consequence : Order is paid, but never shipped.

Steps to reproduce

On some orders (many lately), the payment never gets validated.

Some notifications stays in "In progress" state. Consequence : Order is paid, but never shipped.

Actual behavior

Some notifications stays in "In progress" state. Consequence : Order is paid, but never shipped.

Clicking on "Reprocess Webhook" seems to work.

Expected behavior

All notifications are processed, even if consumer crashes from some reason (I suppose this is the reason, since "Reprocess Webhook" is working - even if I cannot found anything in logs -_-)

Code snippet or screenshots (if applicable)

No response

Adyen Magento Plugin version

10.1.1

Magento version

2.4.8-p2

Operating System

None

Browser (if applicable)

No response

Additional context and logs

No response

[candemiralp]

Hello @Nuranto,

Thank you for creating this issue.

Are you using cron or rabbitmq as the processor? Also, have you seen any error logs on the web server related to the crontab or rabbitmq server related to the processing errors based on your case?

Best Regards,
Can

[Nuranto]

Hi,

Cron & no logs...

[thomascharbit]

Hi,

Upgraded to 2.4.8-p2 + 10.1.1 and i have the same issue with cron handling the notifications.

I get errors like:
Adyen Logger.ERROR: While processing a notification an exception occured. The payment has already been saved in the adyen_order_payment table but something went wrong later. Please check your logs for potential error messages regarding the merchant reference (order id): xxxxxxxxx and PSP reference: xxxxxxxxx. Exception message: Unique constraint violation found [] {"uid":"6cd1668"}
Edit: this is because od the reprocessing of the notification, sorry

If i manually set back processing = 0 in DB, then the notification is correctly processed.

what could be the cause?

[thomascharbit]

From my experience this was due to another module that was triggering errors in the cron queue processor, thus preventing the notifications from being properly handled.
This is working now on my side, sorry about that

[candemiralp]

Hello @Nuranto and @thomascharbit,

We have implemented some improvements and bug fixes on versions 10.5.2, 10.4.0 and 10.3.0. Could you please confirm if this issue is still valid?

Best Regards,
Can