Forum Discussion
Intermittent failures on realtime data stream
I have a realtime data stream that gets intermittent failures. I am trying to figure out the potential cause. below are the error details I am receiving. The refresh is probably working 50% of the time. The script I am using is calling a rest API,parsing the JSON response, saving the data as a variable and then pushing the data into PowerBI. Has anyone else ran into similar issues or may know what could cause an error like below.
HTTP/1.1 500 Internal Server Error
Cache-Control: no-store, must-revalidate, no-cache
Transfer-Encoding: chunked
Content-Type: application/json; charset=utf-8
Server: Microsoft-HTTPAPI/2.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Frame-Options: deny
X-Content-Type-Options: nosniff
RequestId: 8d62de09-6c3b-448a-91e2-37487c960f95
Date: Thu, 28 Jun 2018 19:28:18 GMT
{"error":{"code":"RealTime_PushRowsInvalidJson","pbi.error":{"code":"RealTime_PushRowsInvalidJson","parameters":{},"details":[]}}}
Thank you,
Paul
3 Replies
Hi paulhudgins,
I'd like to recommend to take a loot at below limitation document about REST API:
To POST Rows
- 75 max columns
- 75 max tables
- 10,000 max rows per single POST rows request
- 1,000,000 rows added per hour per dataset
- 5 max pending POST rows requests per dataset
- 120 POST rows requests per minute per dataset
- If table has 250,000 or more rows, 120 POST rows requests per hour per dataset
- 200,000 max rows stored per table in FIFO dataset
- 5,000,000 max rows stored per table in ‘none retention policy’ dataset
- 4,000 characters per value for string column in POST rows operation
Regards,
Xiaoxin Sheng
Anonymous,Thank you for the reply.
Looking at the limitations, my dataset itself shouldn't be near those limitations. This API has 16 defined values and is scheduled to update every 10 minutes. I have another streaming dataset that although it has 7 values defined is set to update every minute and it is never failing. Below is the response from a succesful push. The only difference I see on the header response is the content-type.HTTP/1.1 200 OK
Cache-Control: no-store, must-revalidate, no-cache
Transfer-Encoding: chunked
Content-Type: application/octet-stream
Server: Microsoft-HTTPAPI/2.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Frame-Options: deny
X-Content-Type-Options: nosniff
RequestId: b5a93ec2-30ea-42ca-8629-50228534c00e
Date: Fri, 29 Jun 2018 14:46:56 GMTKind Regards,
Paul
HI paulhudgins,
Actually, I test to send request with utf-8 encode on my side without any issue, maybe you can try to open a ticket for this scenario.
Regards,
Xiaoxin Sheng
