Handle 429s errors
moritzraho opened this issue · 1 comments
moritzraho commented
Expected Behaviour
429s from CosmosDB might arise if RU/s are consumed. State lib should wrap the error to hide the internal CosmosDB error and let the user catch the specific error based on a documented error code.
An optional retry mechanism could be directly implemented in state lib.
Actual Behaviour
The error is unknown to state lib, hence it is not wrapped and the internal cosmosDB error is shown
"_internal": {
"stack": "Error: Message: {\"Errors\":[\"Request rate is large. More Request Units may be needed, so no changes were made. Please retry this request later. Learn more: http://aka.ms/cosmosdb-error-429\"]}\r\nActivityId:
[..]
If the user wants to implement an error mechanism he has to parse the private _internal
field of the error
aiojbot commented
JIRA issue created: https://jira.corp.adobe.com/browse/ACNA-961