Delay (up to 10 s) for “Archive issue” action popup in Slack integration

### Environment

SaaS ([https://sentry.io/]())

### Steps to Reproduce

Clicking the “Archive issue” button on a Slack alert now incurs a 5–10 second delay before the confirmation popup appears, rather than showing immediately.

[https://github.com/user-attachments/assets/f94f7ce0-d7e7-485f-85cf-ffa044b335b1]()

1. In Slack (desktop or web), locate an alert message from the integration.
2. Click the Archive issue button.
3. Observe the time taken for the confirmation popup to appear.

### Expected Result

The “Archive issue” confirmation popup should display almost instantly (under 1 second) after clicking the button.

### Actual Result

There is a delay of approximately 5–10 seconds before the confirmation popup becomes visible and interactive.

### Product Area

Settings - Integrations

### Link

*No response*

### DSN

*No response*

### Version

*No response*

We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples**:**

* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs

---

**Candidate Metrics (add more below)**

* …

*(please also add ideas, questions or examples in comments)*