Slack integration archive button not working: "We had some trouble connecting"

[liamjones]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Have Slack integration sending alerts to a channel.
2. Try to archive issue from Slack

Expected Result

Issue is archived.

Actual Result

Slack always displays "We had some trouble connecting." when the green archive button is pressed.

This might be related to #94399?

Checked with a colleage on a different network and they're seeing the same behaviour.
Checked multiple alert messages in Slack and the button doesn't work on any of them.

Product Area

Settings - Integrations

Link

Slack notification from an alert for this ticket: https://living-with.sentry.io/issues/6837442652/?alert_rule_id=12200292&alert_type=issue&notification_uuid=f42e5cbe-bc94-45ee-904b-556ebd3a7ddb&project=6741433&referrer=slack

DSN

https://4b63bd9c737d442bb328fb649e1be22f@o169785.ingest.us.sentry.io/6741433

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)

[linear]

ENG-5384 Slack integration archive button not working: "We had some trouble connecting"

[getsantry]

Auto-routing to @getsentry/product-owners-settings-integrations for triage ⏲️

[liamjones]

Oh, extra info - it looks like the archiving of the ticket is actually happening in Sentry even with the error message in Slack.

The alert message in Slack doesn't update itself to say it's archived like it normally would though.

[sentaur-athena]

We are aware of this issue. Unfortunately due to current structure of integration and the way slack interaction works, there is no easy way to fix this. As you mentioned the action is successful, the problem is that slack doesn't hear back fast enough and the modal times out.

[sentaur-athena]

Ok just talked to @iamrajjoshi and apparently we have a quick fix to improve this 😅 fix coming up soon.

[iamrajjoshi]

This should be fixed now!