ES /docs

StandardError - wrong number of arguments (given 1, expected 0)

Service
cupixworks-worker
Occurrences
39
Status
Reported
Confidence
95%
Actionability
52%
Cluster ID
c58fdb5a-4fae-401e-8d69-537c95e36a7d
First Seen
2026-06-06 11:13 UTC
Last Seen
2026-06-14 09:34 UTC
Actions

StandardError - wrong number of arguments (given 1, expected 0)

What Happened#

Facility Transfer 작업 중 Progress 레코드를 Elasticsearch에 재색인하는 단계에서 ProgressSerializerArgumentError: wrong number of arguments (given 1, expected 0)를 던졌다. cupixworks-worker (Sidekiq) 환경에서 2026-06-06 ~ 2026-06-08 사이 총 20건이 발생했고, 모두 BulkIndexWorker로 재시도된 뒤 Sidekiq job died after all retries 상태로 종료되었다. 직접적 원인은 progress_serializer.rb:91attribute :record_completed_at, &:record_complete_at 작성 패턴이 Symbol#to_proc의 arity 동작 때문에 fast_jsonapi가 메서드를 1-인자(serialization_params)로 호출하게 만들기 때문이다.

Quick Facts#

Field Value
exception.class StandardError (실제 원인은 ArgumentError)
exception.message wrong number of arguments (given 1, expected 0)
top_frame app/models/concerns/properties/progress.rb:91:in 'record_complete_at'
serializer app/serializers/progress_serializer.rb:91
runtime Ruby 3.3 / Rails (tesla repo)
deploy production-us-west-2-20260605T0515Z0-8562b202-cupixworks
env production / us-west-2
trigger Facility Transfer ([Transfer][854] ... fqgvj ...) → Progress re-index

Affected Teams#

Team / Domain Error Count Impact
cupixworks-worker (Progress indexing / Facility Transfer) 20 Transfer 대상 facility의 Progress 레코드가 Elasticsearch에 갱신되지 않아 검색·통계 결과가 stale 상태가 됨. Sidekiq job들이 retry 후 dead 큐로 이동.

Timeline#

  1. 2026-06-06 20:13 KST — 첫 발생 (first_seen). [Transfer][854] Facility Transfer 작업 도중 Progress _update_document 실패.
  2. 2026-06-06 20:13 ~ 21:00 KST — 첫 번째 burst (Transfer 854 진행 중, 12건).
  3. 2026-06-07 21:57 KST — 두 번째 발생 묶음 (2건).
  4. 2026-06-08 10:22 ~ 10:26 KST — 세 번째 burst, 마지막 발생(last_seen)에서 Sidekiq job died after all retries 기록.

Scoring#

Confidence 95% · Actionability 52%

Confidence#

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

Actionability#

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