You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally, I have observed a notification storm to cause notification to be dropped on the HC end due to rate limiting.
It shows up in the jenkins log as:
HipChat post may have failed. ResponseCode: 403, Response: {"error":{"code":403,"type":"Forbidden","message":"You have exceeded the rate limit. See https:\/\/www.hipchat.com\/docs\/api\/rate_limiting"}}
It would nice to be able to [optionally] queue and retry messages rejected with this HTTP error status.
The text was updated successfully, but these errors were encountered:
Occasionally, I have observed a notification storm to cause notification to be dropped on the HC end due to rate limiting.
It shows up in the jenkins log as:
It would nice to be able to [optionally] queue and retry messages rejected with this HTTP error status.
The text was updated successfully, but these errors were encountered: