ES /docs

Api::V1::CapturesController#reinvoke (avg 11695ms, max 11695ms)

Service
cupixworks-api
Occurrences
25
Status
Reported
Confidence
80%
Actionability
28%
Cluster ID
94ea15c2-a8d7-43c2-b80c-9cac5def791b
First Seen
2026-06-24 17:59 UTC
Last Seen
2026-07-17 00:53 UTC
Actions

Api::V1::CapturesController#reinvoke (avg 11695ms, max 11695ms)

What Happened#

2026-06-25 02:59 KST (17:59 UTC) eu-central-1 region에서 POST /api/v1/captures/40130/reinvoke 요청 한 건이 11,695 ms 동안 처리되며 latency 클러스터로 검출됐다. 해당 요청은 command=reprocess_capture로 들어와 controller 내부에서 동기적으로 CaptureInvoker#reprocess_captureCaptureInvoker#reset_capture 전체 플로우(unpublish, processing job 중단, AWS task stop, panos 일괄 update, refinement/3D reconstruction 재설정, BulkIndex enqueue, Slack post 2회)를 실행했다. status는 200으로 정상 완료됐고 같은 시간대에 5xx 에러나 외부 의존성 장애는 관측되지 않았다.

Quick Facts#

Field Value
exception.class (없음 — 200 OK)
top_frame app/controllers/concerns/invokable/captures_controller.rb:33
resource_name Api::V1::CapturesController#reinvoke
command reprocess_capture (추정 — 11.7s 지연 패턴이 reset_capture 호출 경로와 일치)
target Capture id 40130 (oldest-id, 누적 데이터 많음)
env production, eu-central-1
trace_id 2389808484529763761

Affected Teams#

Team / Domain Error Count Impact
cupixworks-api (Capture reprocess) 1 reprocess 요청한 단일 사용자에게 약 12초의 응답 지연. 데이터 손상은 없음.

Timeline#

  1. 2026-06-25 02:59:31 KSTPOST /api/v1/captures/40130/reinvoke 요청 시작 (cluster last_seen = 2026-06-24T17:59:31.677Z UTC).
  2. 2026-06-25 02:59:43 KSTreset_capture 내부 단계가 거의 동시에 emit됨: "Capture 40130 reset refinement job" / "...reset refinement job done" / "Capture 40130 reset 3d_reconstruction"(2회) / "Capture job is created for capture 40130. job_id: 113483" / "preprocessor agent is invoked for capture 40130" / "invoke capture processing for capture 40130." (Datadog logs).
  3. 2026-06-25 02:59:43 KST — refinement_state refined → draft 전이 로그.
  4. 2026-06-25 02:59:44 KST — 응답 200 완료. 총 소요 11,695 ms (cluster 통계).
  5. 2026-06-25 03:04:59 KST — 후속 처리 시작: "skatmaster is invoked for capture 40130. job id: 113483".

Scoring#

Confidence 80% · Actionability 28%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 12 code refs, 7 log queries
Code path explicitness 3/3 12 file:line refs
Log evidence 2/3 section, query
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 11 file(s)
Single repo 1/3 4 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