Unanswered questions

We have one of our Private External StatusPages no longer sending notification emails.  All other pages are sending the notifications without issue.  The email address that sends the notifications is the same for all pages and is not blocked by our domain server.I have reduced the number of subscribers from 259 down to 3, in increments, checking each time if emails were being sent.  No emails have been sent out.  The confirmation of subscription emails when you add a subscriber are going out for the page though. It was working ok up to 1st December.  Has anyone else had this issue?

We are using the connections configuration for the slack integration  so that incidents get a separate thread in a given channel for a given service.Using the pagerduty api and the slack integration,  I am trying to determine which slack thread a given incident is being tracked in.   I looked at notification channels, but when I query the API get no data back for an incident that should have a thread.   I also looked at dedicated channels, but we are not using dedicated channels in the configuration, so I figured that was not the right place either.If you have done this before or can point me in the right direction. your help would be appreciated

Hello I was wondering what is the data retention policy for the alert as how long alerts/incidents data is kept in the pagerduty. I couldnt find any settings/config for that or any documentation.  Mehran 

I’m noticing a recent change in the mobile app where resolving an incident via swipe now requires an extra confirmation tap. Previously, a single swipe action would immediately resolve the incident with no additional interaction.This new flow adds extra time, especially when handling multiple low-severity or routine incidents. What used to be a quick one-gesture action is now a two-step process, effectively doubling the time required to resolve each incident.Is there a setting, or a way to revert to the previous workflow? I’ve disabled any requirement for resolution notes in the confirmation screen but it still requires that secondary workflow.