It is unclear how best to handle a 429 from CRM. The CRMWebAPIException does not give access to the status code. Even if it did, we would be missing the RetryAfter header. Ideally it would be handled by the library or at least it could be exposed. Maybe a quick fix would be to add the HTTP status code in the exception?
This is somewhat related to #86 but I'm not necessarily looking for integration with Polly.
Also, I currently don't see the retries being handled in PR #99 mentioned by the issue #86 .
It is unclear how best to handle a 429 from CRM. The CRMWebAPIException does not give access to the status code. Even if it did, we would be missing the RetryAfter header. Ideally it would be handled by the library or at least it could be exposed. Maybe a quick fix would be to add the HTTP status code in the exception?
This is somewhat related to #86 but I'm not necessarily looking for integration with Polly.
Also, I currently don't see the retries being handled in PR #99 mentioned by the issue #86 .