recipe deletion failed: {"message":"Forbidden"}
Service
cupixworks-api
Occurrences
321
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
43625c47-fb78-47a2-bb34-061ac3def155
First Seen
2026-04-10 07:23 UTC
Last Seen
2026-07-10 19:14 UTC
Actions
recipe deletion failed: {"message":"Forbidden"}
What Happened#
2026-05-08 07:06:37 UTC에 cupixworks-api 서비스(us-west-2)에서 admin 사용자가 팀 1173의 assigned_customer_success_managers 그룹에서 사용자(ID: 751)를 제거하는 과정에서, 해당 사용자의 notification recipe 삭제가 3건 모두 실패했다. notification-service의 API Gateway authorizer가 user 751의 api_token을 거부하여 {"message":"Forbidden"} 응답을 반환했다.
Quick Facts#
| Field | Value |
|---|---|
| exception.class | Cupix::NotificationService |
| exception.message | recipe deletion failed: {"message":"Forbidden"} |
| top_frame | lib/cupix/notification_service.rb:65 |
| env | production, us-west-2 |
| deploy | production-us-west-2-20260508T0527Z0-cc7eab2d-cupixworks |
Timeline#
- 07:06:37Z — Admin user (daniel.kim@cupix.com)가
PUT /api/v1/admin/teams/1173/groups/assigned_customer_success_managers/remove_users호출 - 07:06:37Z — User 751의 cached permissions flush 실행
- 07:06:37Z —
UserRecipeCleaner가 3개 recipe 삭제 시도 (facility_new_project,record_processing_completed,record_preview_ready) — 모두 Forbidden으로 실패 - 07:06:37Z — 전체 HTTP 요청은 200으로 정상 완료 (recipe 삭제 실패는 비차단 부작용)
Scoring#
Confidence 85% · Actionability 28%
Confidence#
| Dimension | Score | Detail |
|---|---|---|
| Evidence completeness | 5/5 | 17 code refs, 4 log queries |
| Code path explicitness | 3/3 | 17 file:line refs |
| Log evidence | 3/3 | section, query, pattern |
| RCA structure | 3/3 | 3/3 sections |
| Revision history | 0/3 | 0 revision(s) |
| Agent execution | 3/3 | success |
Actionability#
| Dimension | Score | Detail |
|---|---|---|
| Fix complexity | 1/5 | critical |
| Affected files | 1/5 | 14 file(s) |
| Single repo | 1/3 | 3 service(s) |
| Immediate actions | 0/3 | absent |
| Testability | 0/3 | no test info |
| External dependency | 1/3 | external deps found |
| Data migration | 3/3 | no migration |