question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Throttle Exceeded error incorrectly reported

See original GitHub issue

When QuickBook’s rate limit is exceeded the client receives the error response but raises the exception for when it cannot read the json response instead of reporting that the request limit has been reached. Provided below is the exception thrown when this occurs:

QuickbooksException: Error reading json response: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<IntuitResponse time="2016-10-10T12:14:28.801-07:00" xmlns="http://schema.intuit.com/finance/v3">
    <Fault type="SERVICE">
        <Error code="3001">
            <Message>message=ThrottleExceeded; errorCode=003001; statusCode=403</Message>
            <Detail>The request limit was reached.  Try again later</Detail>
        </Error>
    </Fault>
</IntuitResponse>

It looks like this is happening because the make_request method in the QuickBooks object expects both success and error response to return json but for the ThrottleExceeded error QuickBooks responds with xml.

I am using version 0.5.1 of the library and a sandbox instance on QuickBooks.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
ej2commented, Jan 27, 2017

According to Intuit the Requesting json, receiving XML errors issue has been fixed.

0reactions
ryphillcommented, Nov 3, 2016

Small update on this from QuickBooks. The throttle error is handled by their Gateway service layer and they have filed an internal issue to address this bug. I will provide any updates from QuickBooks as I receive them.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Hello, we are getting error 429 Throttle Exceeded errors but it ...
Hello, we are getting error 429 Throttle Exceeded errors but it does not appear we are exceeding any of the API Limits which...
Read more >
Resolve IAM and STS rate exceeded throttling errors
Follow these best practices to avoid throttling errors. Implement exponential backoff in your application's code. Exponential backoff allows longer waits each ...
Read more >
Throttling: Rate exceeded · Issue #5637 · aws/aws-cdk - GitHub
The CloudFormation runs just fine, but CDK returns an error because the rate limit was exceeded. We're using typescript. The issue #1647 says ......
Read more >
Handle throttling problems, or '429 - Azure Logic Apps
Throttling can create problems such as delayed data processing, reduced performance speed, and errors such as exceeding the specified retry ...
Read more >
You have exceeded the call threshold per second. Please ...
You have exceeded the call threshold per second. Please throttle traffic for this call and then retry. Getting error as 'You have exceeded...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found