Issue Summary

Originally we identified this as if you had more than 8 pages of inactive Services in your Pager Duty setup, an error will be thrown that says " Yikes! We're having trouble connecting to PagerDuty. Maybe try back again in a few minutes?"

However, we have since identified that this can occur at any time with a subset of characters that are included in the Pager Duty inactivate services list.

Steps to Reproduce

1. Go into your Pger Duty setup from the "Apps" menu
2. Go to your Inactive Services column
3. Scroll through your services and you will get the error
   

Expected Results

• Being able to scroll though all of the pages without issue and view all the inactive services

Actual Results

• We identified that when Statuspage cannot render the name of service because of the returned characters, it will throw this error: 
  " Yikes! We're having trouble connecting to PagerDuty. Maybe try back again in a few minutes?"
• Other services will be available on additional or previous pages, and when this error is encountered it will consider this page done, and the next service will be rendered on the next page of services. (It creates a pagination break in the list of services)

Workaround

None at the moment