[google-checkout-api-uk] Re: Still getting order-state-change-notification for archived orders over 2 weeks old (sandbox) - imgiseverything - com.googlegroups.google-checkout-api-uk

4 messages in com.googlegroups.google-checkout-api-uk[google-checkout-api-uk] Re: Still ge...

From	Sent On	Attachments
imgiseverything	28 May 2008 06:50
Simon	28 May 2008 08:17
imgiseverything	28 May 2008 08:22
imgiseverything	28 May 2008 08:33

Subject:	[google-checkout-api-uk] Re: Still getting order-state-change-notification for archived orders over 2 weeks old (sandbox)
From:	imgiseverything (hel...@philthompson.co.uk)
Date:	05/28/2008 08:22:55 AM
List:	com.googlegroups.google-checkout-api-uk

Thanks for responding so quickly, I'm not sure my lack of response is an issue - not accordingly to me log file.

I have an acknowledgement after the notification (at the same time) for all 5 notifications.

An example (bulk of notification elements omitted for brevity): =========== Wed May 28 12:12:51 BST 2008:- <?xml version="1.0" encoding="UTF-8"?> <new-order-notification xmlns="http://checkout.google.com/schema/2" serial-number="759290672594522-00001-7"> <timestamp>2008-05-28T11:12:10.658Z</timestamp> <snip /> </new-order-notification>

Wed May 28 12:12:51 BST 2008:- <?xml version="1.0" encoding="UTF-8"?

<notification-acknowledgment xmlns="http://checkout.google.com/schema/

2"/>

=======

Phil

On May 28, 4:18 pm, Simon <simo...@gmail.com> wrote:

HI. I think both these issues have the same underlying cause.

When Google send you a notification, you are required to respond with at least an HTTP 200 response code (and preferably a <notification- acknowledgment>) within 10 seconds. This 10 seconds includes the complete network round trip. If you fail to send such a response, Google will keep sending the notification until you do so. The frequency tails off with time. So Google may send the notification a few times in the first day and then send it less frequently until such a time as they give up (after 30 days I think).

If you are having problems in replying in 10 seconds, you may like to read this for more
information:http://code.google.com/apis/checkout/developer/Google_Checkout_XML_AP...

thanks S...

On May 28, 2:51 pm, imgiseverything <he....@philthompson.co.uk> wrote:

After quite a bit of struggling, I've finally got Google Checkout's notification API working (a bit) and I think I understand it.

However my log file, is showing that today I've been getting order- state-change-notifications for archived orders which over 2 weeks old. Now this is fine - it doesn't affect my system as these notifications aren't sending nay new information but I can't imagine it's correct that i should be getting callbacks on such old orders which have not changed.

An example (from googlemessage.log)

========= Wed May 28 13:36:17 BST 2008:- <?xml version="1.0" encoding="UTF-8"?> <order-state-change-notification xmlns="http://checkout.google.com/ schema/2" serial-number="734915112697802-00008-1"> <timestamp>2008-05-02T10:13:19.106Z</timestamp> <google-order-number>734915112697802</google-order-number> <new-fulfillment-order-state>PROCESSING</new-fulfillment-order- state> <new-financial-order-state>CHARGING</new-financial-order-state> <previous-fulfillment-order-state>PROCESSING</previous-fulfillment- order-state> <previous-financial-order-state>CHARGEABLE</previous-financial-order- state> </order-state-change-notification> ============

This order is in my archive with the following dates:

Sold on 2 May 2008 11:13:16 GMT+01:00 Charged on 2 May 2008 11:13:19 GMT+01:00 Confirmed on 2 May 2008 11:13:19 GMT+01:00

Also...

I also seem to be getting numerous identical new-order-notifications for the same orders coming through every 30-60 seconds but failing to get the relevant order-state-change-notifications to say the order is chargeable/charging/charged/etc. I got 5 identical new-order- notifications for an order (id: 759290672594522) today in 2 minutes (12:12 - 12:14pm)

Any ideas?