CPUtils#fetchWithRetry per-attempt timeout too low — 1000ms

What Happened#

2026-07-03 17:43:31 KST 프로덕션 cupixworks-api (us-west-2)에서 pub/sub subscriber가 facility_permission 이벤트 처리 중 notification-service의 PUT /api/v1/subscriptions 와 POST /api/recipes/v2를 호출했으나 모두 API Gateway 403을 받았다. 동시간대 notification-service Lambda authorizer 로그에서 Fetch attempt 1/3 ~ 3/3 failed: This operation was aborted가 관측되며, 최종적으로 Error authorizing: This operation was aborted가 남아 authorizer가 isAuthorized: false를 리턴했다. 같은 authorizer timeout 패턴은 최근 24 시간 동안 notification-service에서 반복적으로 관측된다.

Quick Facts#

Affected Teams#

Timeline#

1. 2026-07-03 17:43:27 KST — notification-service authorizer fetchWithRetry 1 회차 abort (0009e416 Fetch attempt 1/3 failed: This operation was aborted)
2. 2026-07-03 17:43:29 KST — retry 2 회차 abort
3. 2026-07-03 17:43:30.211 KST — retry 3 회차 최종 실패, authorizer catch 블록이 Error authorizing: This operation was aborted 로깅 후 { isAuthorized: false } 반환 → API Gateway가 403 응답 생성
4. 2026-07-03 17:43:31.099 KST — cupixworks-api Cupix::NotificationService#create_user_recipe × 3 실패 (recipe_name = record_preview_ready, record_processing_completed, facility_new_project), error_response: {"message":"Forbidden"}
5. 2026-07-03 17:43:31.100 KST — cupixworks-api Cupix::NotificationService#subscribe 실패, rescue 블록에서 e.response를 로그 message로 남김 → cluster fingerprint 대상 로그

Scoring#

Confidence 85% · Actionability 36%

Confidence#

Actionability#