ES /docs

Editing split failed: Couldn't find Editing with 'id'=5549

Service
cupixworks-worker
Occurrences
1
Status
Dismissed
Confidence
85%
Actionability
60%
Cluster ID
a63e1126-98e5-476c-9008-f47bf69e5ef2
First Seen
2026-07-05 09:44 UTC
Last Seen
2026-07-05 09:44 UTC
Datadog↗ Slack↗
Actions
현재 상태 dismissed 에서는 실행할 액션이 없습니다.

Editing split failed: Couldn't find Editing with 'id'=5549

What Happened#

2026-07-05 18:44 KST, cupixworks-worker(Sidekiq) 의 EditingSplitWorker#perform가 editing_id=5549로 실행되었으나 해당 Editing 레코드는 이미 2일 전(2026-07-03 19:43 KST)에 FlushCycleStateChildrenWorker에 의해 삭제(cycle_state=deleted)된 상태였다. 결과적으로 Editing.find(5549)가 ActiveRecord::RecordNotFound를 발생시켜 워커가 실패했으며, 동일 시각 LogEditingStateWorker와 SavePartialJsonToFileWorker도 같은 원인(row missing)으로 각각 “editing not found”/“not found after 6 retries” 로그를 남겼다. 발생 횟수는 1건, 리전은 ap-southeast-1.

Quick Facts#

Field Value
exception.class ActiveRecord::RecordNotFound
exception.message Couldn't find Editing with 'id'=5549
top_frame app/services/cupix/editing_split_service.rb:13
env production / ap-southeast-1

Affected Teams#

Team / Domain Error Count Impact
cupixworks-worker (SiteInsights / Editing split) 1 단일 Editing(5549)에 대한 split 잡 실패. 이미 삭제된 editing이므로 실질적인 유저 영향은 없으나 error 로그 노이즈로 인해 알림 신뢰도 저하

Timeline#

  1. 2026-06-27 17:52 KST — Editing 5549에 대한 generate_partial_json이 정상 실행되며 편집이 활발히 사용되던 시점.
  2. 2026-07-03 19:43 KST — FlushCycleStateChildrenWorker가 Editing 5549의 children을 deleted로 flush ("end flushing children to deleted for Editing ID: 5549"). Editing row가 실질적으로 사라진 시점.
  3. 2026-07-05 18:44:29 KST — 오래 지연된 상태 전이 이벤트("state has transitioned from waiting to ready on Editing 5549")가 실행됨.
  4. 2026-07-05 18:44:29 KST — LogEditingStateWorker info "editing not found: 5549" (deleted row에 대한 find_by=nil).
  5. 2026-07-05 18:44:29 KST — SavePartialJsonToFileWorker가 retry 1 시작, EditingSplitWorker가 동일 시각에 Editing.find 실패로 에러 발생.
  6. 2026-07-05 18:44:35 KST — SavePartialJsonToFileWorker가 6회 재시도 후 "Editing with id 5549 not found after 6 retries" 최종 실패.

Scoring#

Confidence 85% · Actionability 60%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 15 code refs, 5 log queries
Code path explicitness 3/3 15 file:line refs
Log evidence 2/3 section, query
RCA structure 3/3 3/3 sections
Revision history 1/3 1 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 5/5 trivial
Affected files 1/5 19 file(s)
Single repo 1/3 3 service(s)
Immediate actions 0/3 absent
Testability 2/3 test mentioned
External dependency 3/3 no external deps
Data migration 3/3 no migration