check_voxels_uploading S3 ListObjectsV2 high latency

Now I have the cluster details. Let me invoke the RCA skill.

This is a latency cluster for `Api::V1::PointcloudsController#check_voxels_uploading` averaging 2292

Now let me search Datadog logs and explore the tesla repository for the controller code.

I notice the Datadog trace shows it as `Api::V1::PointcloudsController#check_voxels_uploading` but t

The repository delegates to `@model.check_voxels_uploading`. Let me find the model method that does

Now I can see the performance issue. The `check_voxels_uploading` method calls `voxels_object_key_li

Now I understand the full code path. The `check_voxels_uploading` method calls `list_objects_v2` on

Now let me search for more information about the storage_option and the region configuration, and al

Now let me look at the `storage_option` to understand the region configuration and check the `done_v

Now I have the full picture. The `done_voxel_state` triggers state transitions which include `increa

Excellent! The metrics confirm the latency issue — values up to 6.99 seconds in `ap-southeast-2`. No

Now let me look at the `Pointcloud` model specifically and its database-saving behavior after `done_

Now I have a complete understanding. Let me also check the `before_transition to: :done` callback th

Now I have all the evidence I need. The latency comes from:

Interesting — those "Voxels uploading is done" logs are from `us-west-2` region. But the cluster is

The metrics confirm significant latency spikes in `ap-southeast-2` — values ranging from 1.1s to 6.9

Good, the directory exists. Let me write the RCA report.

Now let me update the cluster frontmatter (rca_status only). Let me first check the current frontmat

The user instructed "Do NOT modify the cluster frontmatter — the pipeline manages the status field."

RCA report written to `./content/docs/incidents/2d88d0bf-94d6-4f3b-a419-b9a830e976e0/rca.mdx`.