1 / 8
Apr 2015

Noticed in the last couple days that the transactions log was slow to load. This morning it will not load at all. Other parts of the site appear to be working normally (i.e. view/edit delete products and re-activate expired links). I haven't tested anything else.

  • created

    Apr '15
  • last reply

    May '15
  • 7

    replies

  • 1.6k

    views

  • 4

    users

Sorry for the trouble, during high traffic periods the transactions log can be slow to load, particularly for large reports. If you are having trouble accessing it we recommend waiting for a little bit before trying again, since repeated reloads will actually only increase the traffic strain and slowdown.



Everything seems to be moving smoothly right now, if you are still experiencing problems now please let us know.

26 days later

Once again I find that my transaction log won't load. It's difficult to provide my customers with timely customer service when I can't rely on the transaction log to load.

It seems to be working fine now. Whenever the log won't load, that typically means someone else has tied up the log server running a query with a huge number of transaction results, so until that query returns all its results to that user, everyone else's queries wind up waiting in line.



For this reason, we recommend running log queries to be as specific as possible -- e.g., ideally you'd have a specific Transaction ID or buyer name/email to search, or you can run a query for just the specific date range and/or product you're looking for. For customer service with a particular buyer, you could also search your own email records for the buyer's name/email in the Sale Notification emails we send you every time we process an order for you.

By not loading, I mean the transaction log page itself, before I can even put in any criteria for a search.



The page just came up now, it probably took about 60 seconds for the page to load. (no, I'm not having internet connectivity problems with my ISP, everything else on my end is loading fast).

Yes, that's just the way it behaves when someone else already has the log server completely tied up running a huge query of their own. Once that query finally concludes and frees up the log server, that allows the log page to finally load for other users who've been waiting in line, allowing you to view your log at that point and run your own custom query if you wish.