Issue Summary

Error message is populating within the Statuspage/Pagerduty setup "Yikes! We're having trouble connecting to PagerDuty. Maybe try back again in a few minutes?" This is differrent to the already existing bug: https://jira.atlassian.com/browse/STATUS-713.

It has been investigated into that there could be a discrepancy in the count of services from Pagerduty to Statuspage contributing to a pagination issue which then returns the error message.

Steps to Reproduce

Create a lot of services on Pagerduty. The services will reflect on Statuspage manage portal once we configure pagerduty integration for them. Configure some active services for the instance on manage.

Then remove some services from Pagerduty. 

Expected Results

Count of inactive + active services on manage should match the total number of services on pagerduty. 

Actual Results

Count is different. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available