Api::V1::EditingsController#show (avg 1580ms, max 1580ms)

Now I have the cluster details. This is a latency cluster for `Api::V1::EditingsController#show` wit

Let me search Datadog logs and explore the source code in parallel.

The logs show 200 OK responses, no errors. This is a latency cluster (1580ms response time). Let me

Found the slow request — editing ID 1122847, trace ID matches. Now let me explore the controller cod

The `show` action uses the `set_editing` before_action which calls `repository_instance.show(params[

Now let me look at the `BaseRepository#show` method and the `_record` method in the serializer which

Now let me look at the class-level `show` method in `BaseRepository`:

Now I can see the `show` method at line 308-386. It does `default_joins` + `permission_joins`. Let m

Now let me look at how the `_record` attribute is computed in the `EditingSerializer` context. Let m

The `_record` is likely defined in a concern or the model itself. Let me look at CupixSerializer and

Let me look at how `_record` is defined on the Editing model and what `HasEditingEntityController` d

Let me now look at the `RecordEntity` module that it includes and the `_record` attribute that the s

Now let me find the `_record` method that the serializer uses (`attribute :record, &:_record`):

The `_record` is not a defined method — it must come from a dynamic/association delegation. Let me l

So `Editing` belongs_to `:record`. The serializer uses `&:_record` which calls the `_record` method.

The `_user`, `_record`, `_editor` etc. must be defined in a concern related to serializable/model at

The `&:_record` syntax passes a proc that calls `_record` on the model instance. Let me check the `F

These aren't defined on the model. They must be in the `FacilityEntity` concern or generated dynamic

Let me look at the serializer attribute concerns that define `_record`, `_user`, etc. — these are li

So `_facility`, `_record`, `_user` etc. are all methods that get called on the model. Let me check i

Let me look at where `_facility`, `_user`, `_record`, `_team` methods are defined — likely in `Appli

Found it. Let me read more context around this:

Now let me see the `fetch_cache` method:

Excellent! Now I understand the full picture. The `_record`, `_user`, `_editor` etc. use `fetch_cach

Now let me look at the `permission_joins` for Editing (the one in `EditingRepository` just passes th

Now let me look at the Editing-specific cachable and see what's serialized when the editing's associ

Now I have the cluster details. This is a latency cluster for `Api::V1::EditingsController#show` wit

Let me search Datadog logs and explore the source code in parallel.

The repo-mapping confirms `cupixworks-api` maps to the `tesla` repository at `$REPOS_DIR/tesla`. Now

The metrics show the endpoint typically runs at 50-195ms (average ~80ms), not 1580ms. This was a sin

Now let me look at the `BaseRepository#show` method and the `render_api` method to understand how `s

Now I can see the full code path. The `show` action involves:

These serializer methods like `_user`, `_editor` etc. are likely defined as part of the `CupixSerial

The serializer uses `FastJsonapi::ObjectSerializer`. The `&:_user` syntax calls methods on the model

These must be `method_missing` or delegated. Let me check the `Properties::Editing` concern since th

The `_user`, `_editor`, `_record` etc. are likely defined by a common serializer helper. Let me look

Let me search for where `_user` is defined as a model instance method - it may be in a concern that'

Now I understand the caching layer. The `_user`, `_editor` etc. in the serializer are fetched via ca

The `_user`, `_editor`, `_record` methods are not from the cache concern directly. They must be defi

These methods aren't explicitly defined anywhere as standard Ruby methods. The serializer uses `&:_u

So they all call `&:_team` etc. Let me look at the ApplicationRecord level or see if there's a commo

These aren't the droids we're looking for. Given the `default_joins` selects columns like `team_name

I've done enough code exploration. The `_user` etc. are likely generated by a metaprogramming patter

Now I have the full picture. The `show` action:

Now I have the cluster details. This is a latency cluster for `Api::V1::EditingsController#show` ave

Now let me search Datadog logs for the slow trace and explore the source code in parallel.

I can see the endpoint is returning 200 successfully. Let me search for APM trace data and look for

Now let me look at the specific code paths more closely. Let me read the key files from the tesla re

Now let me look at the StatAttribute concern which could be a significant performance factor, and al

Now let me look at the `_user` method pattern and how associations are resolved via the Cachable con

Let me check how the `_user` and similar methods are defined — they're likely generated via `belongs

Now I have a clear picture. The `_user`, `_editor`, `_level`, etc. methods all call `fetch_cache` wh

Good — `stat_total_entities`, `stat_total_changed`, `stat_total_reviewed` are columns on the `editin

Directory exists. Now let me write the RCA report.

RCA report written to `./content/docs/incidents/4991d698-c7e5-40a0-83c5-5772140f49ba/rca.mdx`.

RCA complete. The report is at `./content/docs/incidents/4991d698-c7e5-40a0-83c5-5772140f49ba/rca.md