You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case an Adobe Commerce order is placed by using the Adyen payment method and the order status is changed to the one that can't be held by checking in that place
if ($this->forterConfig->forceHoldingOrders() && !$order->canHold()) {
the Adyen Authorization webhook that is created on the Adobe Commerce side can't be processed when the order is held. This is stuck in processing status and does not finish updating all Adyen DB tables with the necessary data to be used in the PostDecisionActions cron run.
Could you please fix the logic that allows to execution decline handler on the Adobe Commerce side only in the case when Adyen Authorization webhooks are processed and all data from Adyen is successfully placed in DB?
The text was updated successfully, but these errors were encountered:
In case an Adobe Commerce order is placed by using the Adyen payment method and the order status is changed to the one that can't be held by checking in that place
forter-magento2/Observer/OrderValidation/PaymentPlaceEnd.php
Line 328 in a309b29
That leads to the impossibility execute
forter-magento2/Observer/OrderValidation/PaymentPlaceEnd.php
Line 331 in a309b29
entity type
with valueorder
forter-magento2/Observer/OrderValidation/PaymentPlaceEnd.php
Line 367 in a309b29
As a result, this Ferter entity will not be selected to be processed on the
PostDecisionActions
cron run hereforter-magento2/Cron/PostDecisionActions.php
Line 122 in a309b29
At the same time when is used to force order-holding configuration
forter-magento2/Observer/OrderValidation/PaymentPlaceEnd.php
Line 324 in a309b29
PostDecisionActions
cron run.Could you please fix the logic that allows to execution decline handler on the Adobe Commerce side only in the case when Adyen Authorization webhooks are processed and all data from Adyen is successfully placed in DB?
The text was updated successfully, but these errors were encountered: