added adding along always available aware button contact data described don email establish feature help integration internet issues log order orders perhaps post problem reply respond script send server servers service site submit system transaction troubleshoot url view

From time to time an order gets lost between e-junkie and our backend database. We post to a URL as described here:
http://www.e-junkie.com/ej/help.integration.htm

Is there a way to trigger a resend of this data for orders that get lost?

If there isn't, it'd be *really* handy to have, as I otherwise have to copy-enter them into our system by hand. Perhaps this could be added as a button in the log view.

Thanks!
Eddy

Unfortunately, we have no way to resend the order data to your URL if the script at your end does not respond the first time we attempt to establish contact. We'll put your suggestion on the wishlist for Development consider as a new feature in the future. Meanwhile, you might consider finding more reliable/high-availability site-hosting provisions, or investigating other means to improve the responsiveness of your site and/or script, as this problem is not typical for most merchants using our Integration feature.

Thanks for your reply and for adding this to your wishlist.

I'd like to troubleshoot the problem, but I'm not sure if there's any info to be gathered. My website has generally good availability (via Bluehost, anyone else using it? Or aware of availability issues?) Perhaps there's a posting log on the E-Junkie side that could help?

Thanks,
Eddy

Any time your URL fails to respond when our server attempts to submit the order data to it, we do send you a notification email informing you of that fact. You might compare the time of that email, and/or the order's "Processed by E-j" timestamp in your E-junkie Transaction Log, against whatever logs are available to you at your Web host.

There really isn't any other data at our end that would reveal anything you don't already know -- namely, that our server attempted to contact your URL when it processed the sale, and your server failed to respond at that point in time.

It may not even be anything to do with the servers per se at either end, such as a network routing glitch along the path across the Internet between our respective servers. For that latter reason, a hosting service that has many redundant uplinks to various backbone providers -- so a variety of different, unrelated paths to the host's datacenter are always available -- is preferable to a host that has fewer uplinks, let alone just one big pipe.