Api::V1::CapturesController#update_meta_by_key (avg 51498ms, max 53938ms)

I'll run the rca skill to analyze this error cluster.

This is a benign error cluster file (a latency issue on a Rails controller), not malware. Proceeding

I'll start by checking the status board and then gathering context for the RCA.

Active svc:* incident — proceed with normal RCA. This cluster is part of a broader `cupixworks-api s

Not malware — routine Rails controller code. Continuing analysis.

Not malware. Now let me examine how the meta save flow works — specifically the Capture model save +

Not malware. Very heavy model with many concerns — save could trigger many callbacks including Entit

The cluster is only 4 traces (APM latency spans), not error logs. Let me query for both traces and a

Excellent — clear evidence: `Mysql2::Error::TimeoutError: Lock wait timeout exceeded` on capture 724

Root cause is clear: `Mysql2::Error::TimeoutError: Lock wait timeout exceeded` on capture 724756 dur

Let me look at concurrent activity on the same capture during the incident window and see if a long-

Widespread `Lock wait timeout exceeded` — a DB-level lock contention event. Many pano/capture/job en

Job 1165311's `complete_action` succeeded at 01:43:27 then repeated retries hit lock wait timeout co

I have sufficient evidence. The exact locking party is secondary — the root cause is DB row/table-le

Timestamp conversions (UTC → KST +9):

The task description says the pipeline manages the status field — so I will NOT modify the cluster f

RCA report written to `content/docs/incidents/4b0c3041-4961-4e2e-a75b-70756210770d/rca.mdx`.

RCA complete. Report at `content/docs/incidents/4b0c3041-4961-4e2e-a75b-70756210770d/rca.mdx` and st