Sample Deliverable

프로덕션 버그 트리아지 샘플

실제 고객 데이터가 아닌 가상 예시입니다. 유료 트리아지에서는 이런 식으로 증상, 증거, 원인 후보, 다음 조치를 분리해서 전달합니다.

Input Summary

• 증상: 배포 후 로그인은 되지만 `/api/orders`만 500 응답
• 사용자 영향: 주문 목록 화면이 비어 보임
• 제공된 자료: public stack trace 일부, 최근 PR 링크, 배포 시각

Findings

P1 - API route reads a newly required env var without fallback.
Evidence:
- `api/orders.ts` now creates the service client during module load.
- The deployment log starts failing immediately after import, before request handling.
- Other authenticated routes still return 200, so this is not a global auth outage.

P2 - Frontend masks the server failure as an empty state.
Evidence:
- The list component renders `[]` after catch.
- No visible error message or retry path is shown to the operator.

Not proven:
- Database outage. No evidence yet; health route and unrelated reads still work.
- User token issue. Sign-in and profile route still work.

Next Fix Step

• Move service-client creation inside the handler or validate env at boot with a clear error.
• Return a typed error response for config failures.
• Change the frontend catch path to show an operational error instead of empty data.
• Verify with one direct API call and one browser smoke after deploy.