getsentry / getsentry/sentry

We had some trouble connecting. Try again? error message shown when archiving issue from Slack

Open
#80,181 5 comments 0 reactions 0 assignees View on GitHub
Bug Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

1. Configure the Slack integration.
2. Configure an alert rule to send slack messages on new issues.
3. Trigger the above alert rule.
4. Try to archive an issue via Slack.

### Expected Result

The issue is archived.

### Actual Result

Error message is shown:
![Image](https://github.com/user-attachments/assets/b4c8d3fe-f50c-4a7b-b4f2-c6b63303fc60)

However, in some cases, the issue is still marked as archived in Sentry after the pop-up window is closed:
![Image](https://github.com/user-attachments/assets/ec0123ec-a227-466c-8df2-42bdd370b449)
![Image](https://github.com/user-attachments/assets/8a8b544c-5105-4ccb-810c-cec77fab8551)

### Product Area

Settings - Integrations

### Link

https://dev-curumas.sentry.io/issues/5995189025/activity/?alert_rule_id=15072297&alert_type=issue¬ification_uuid=acdba463-c5a6-4fb8-8dbb-6dab2ffbf358&project=5242419&referrer=slack

### DSN

_No response_

### Version

_No response_

Contributor guide

Open the contributing guide

Research direction

Start at the Slack integration's archive-issue action described in the reproduction steps and trace the request through the Settings - Integrations area. Reproduce the flow against the linked Sentry issue, then verify that archiving succeeds without the misleading error and that the issue remains archived after dismissing the popup.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.