Application Error occurs sometimes

Hi Josef

I'm sorry to hear you're having issues.  Oddly that error indicates that the problem is in fact at the router level, and not at our application level i.e. if we presented an error it would be in a suitable JSON format, and our error logging system would have notified us, which unfortunately it didn't.

I can certainly investigate, but could you answer a few questions:

• You mention you're using the API to retrieve a few backlogs, do you do this synchronously or asynchronously.  I'm just trying to get a handle on how many concurrent requests we may be dealing with as the stats requests are actually a little server intensive.
• Can you send me a sample `curl` command so that I can see how you are accessing the stats.  Obviously please exclude your API key ID.

Thanks for your fast reply!

Currently i am using synchron requests.

I will change this to asynchron requests today and monitor the API calls' output.

@CURL command

Well actually I suspect asynchronous requests might make it work as you will be hitting our application servers harder concurrently.

We are not around today unfortunately, so will look into this on Monday.

Thanks,
Matt

I have implemented the requests as asynchronous requests and will have a look onto the logfile the next days.

:)

Hi Josef

I have found the error in our log files, and it's a performance related issue.  The router is timing out and the process is being killed because it's taking too long to perform this operation.  We will replicate this issue internally and find a solution.  Thanks for notifying us of the problem, and sorry for the inconvenience.

Matt