Canvas errors randomly experienced if REST API semaphore exhaustedSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } - The Next Experience use the REST API for Polaris UI. - If there is any integration Application or other Application that can exhaust the REST API semaphore, a Canvas error will pop up. Symptoms: 1. The session is slow when the issue happens. 2. The instance's overall health may look good. 3. The issue may be intermittent since the Application uses the REST API heavily may run periodically. 4. The Canvas errors don't show up without Polaris Frame. 5. Can see 429 errors in the browser Network tab for Requests.