Developer forum

Forum » Ecommerce - Standard features » Order in limbo

Order in limbo

Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi,

 

We ran across an issue we can't explain, after an order which apparently went to checkout handler successfuly, but then something happened and not the order is not complete (nor is it a cart), nor do we have info on the transation number.

  • All orders before and after this one had no issues
  • There hasn't been any updates on that period
  • There are no notification subscribers for OrderComplete
  • The authorization (number) (aka Transaction number) exists in the Payment Provider (Authorize.net), but it was never updated on the order in Dynamicweb

 

If you look at the attached image, you'll start seeing the error message "The Context.GetCart() is not a cart..." and that has hundreds of occurences suggesting a loop of a set of retries that lasted for about 3min populating 9 pages worth of logs (from 12:37:08 until 12:40:17)

 

Has anyone ever experienced something like this? Any ideas on how can I track this down further?

 

I guess I can force/update the values of the transaction number, transaction amount and some others to try and fix the order in Dynamicweb and capture the amount, but I wonder what could have caused this.

 

Best Regards,

Nuno Aguiar

2022-01-10_11-12-27.jpg

Replies

 
Adrian Ursu Dynamicweb Employee
Adrian Ursu
Reply

Hi Nuno,

We have seen this before but we could not create a valid scenario to reproduce it in order to create a valid request to Dynamicweb Support. Not always this process results in a ghost order. Sometimes the order is fine even with these multiple requests. In our case, the solutions are running on DW 9.9.x

 

 
Nicolai Pedersen
Reply
This post has been marked as an answer

It is a sync issue that happens rarely if both the receipt and the callback happens at the same time.

I believe this is fixed in later 9.10 versions

Votes for this answer: 1
 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Nicolai and Adrian,

 

Thank you for the information. Skimming the bug fix list seems to be fixed in 9.10.17 + 9.12.2 (#4873).

 

Best Regards,

Nuno Aguiar

 

You must be logged in to post in the forum