Skip to main content
Announcements
See why Qlik is a Leader in the 2024 Gartner® Magic Quadrant™ for Analytics & BI Platforms. Download Now
cancel
Showing results for 
Search instead for 
Did you mean: 
lachlanwcast
Partner - Contributor III
Partner - Contributor III

REST connector randomly failing with "ResponseEnded"

Hi there,

We have an a script that loads data from Xero using a REST API (and Qlik REST connector) in Qlik SaaS.

What seems to be completely random, an API call will hang for a short period (anywhere between 20 and 60 seconds) and then return an error message as below:

"RestConnectorMasterTable << RestConnectorMasterTable
Data has not been loaded. Please correct the error and try loading again.
The following error occurred:
(Connector error: The response ended prematurely, with at least 10532 additional bytes expected. (ResponseEnded))
The error occurred here:
RestConnectorMasterTable:"

The additional bytes figure also varies.

If we keep retrying the script, eventually it will work but this may not by successful until the 10 or 15th retry.

What does "The response ended prematurely" indicate technically in the REST connector? Could this be an issue with Xero or a networking issue between Qlik SaaS and the Xero API or timeout related?

I haven't found any other posts that mention this particular error which leads me to believe it's either a networking issue or an issue with the Xero API

Thanks in advance for any assistance!

 

Labels (2)
2 Replies
VesaLukka
Contributor II
Contributor II

Sounds like Xero is denying access temporarily. Perhaps Your load script exceeds Xero's minute limit, 60 calls per minute? 

API's limits founds here:  OAuth 2.0 API limits — Xero Developer

Use Postman (or other tool) to see what is http status code. Code 429 is too many requets. All other Xero's status codes: Accounting API HTTP Response Codes & Errors — Xero Developer

 

If script makes too many calls too fast You should read from Xero in smaller bacthes.

lachlanwcast
Partner - Contributor III
Partner - Contributor III
Author

That is what we thought - but the Qlik REST connector is not returning any HTTP codes for us to validate that.

We do smaller batches, and slow the requests down to keep under their API limits (and when we check the headers we are under their limits) so looks like it is something else...

Thanks for your response, appreciate you taking the time!