Issue Grouping settings Stack Trace Rules are applied after restarting sentry-taskworker conteiner
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
### Self-Hosted Version
25.11.1
### CPU Architecture
x86_64
### Docker Version
27.3.0
### Docker Compose Version
2.29.2
### Machine Specification
- [x] My system meets the minimum system requirements of Sentry
### Installation Type
Fresh install
### Steps to Reproduce
1. Add Stack Trace Rules from UI
2. Save button
3. Applying after restart docker conteiner sentry-taskworker
### Expected Result
Applying Stack Trace Rules after click save button
### Actual Result
logs in sentry-web conteiner
[INFO] sentry.utils.exceptions: No task state found in exception_grouping_context
### Event ID
_No response_
Contributor guide
Research direction
Reproduce the issue by creating Stack Trace Rules in the UI, saving them, and restarting the sentry-taskworker container. Start with the sentry-taskworker and sentry-web logs, including “No task state found in exception_grouping_context.” Done means saved rules apply immediately after saving and continue to apply after the worker restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100