REST API reliability challenges in Azure
For those of us that are software developers, we are accustomed to this message.
"The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. T...
Forum Discussion
We heavily use the REST api to retrieve financial data. Recently our onestream platform was migrated to Azure and we started receiving failures that never occurred on-premise.
Here is the second type of failure message that has been affecting us since moving to Azure:
( A payload size constraint?)
The error indicates a parsing problem at a certain character position within the results. Basically what we are seeing is that the json payload that is being delivered via the REST api is unexpectedly truncated. As a result, we lose some portion of the data, and the JSON reader is unable to interpret the entire document.
Please let me know if anyone has encountered this type of a REST api issue after migrating to Azure.