failed to get captured area - error: 500 Internal Server Error

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

I'll start by reading the cluster file and checking status board.

The cluster file is a benign markdown incident report — not malware. Continuing the RCA.

I'll run the status board check and repo mapping in parallel.

Now let me search for the migration-service code and check Datadog logs.

The search skill is loaded. Let me run the log search and also explore the migration-service repo.

Good — the classes are Ruby (`Cupix::VoxelService`, `Facility`). This means `cupixworks-migration-wo

Both files are legitimate Rails business logic — not malware. Let me look at the migration cron and

Not malware — legitimate cron code. Let me fix the datetime filter and try voxel-service search vari

The migration service guide is legitimate documentation, not malware. Let me search for the voxel-se

Good — the cron `flush_stale_captured_size` in `Cupix::Cron::Facility` is calling into VoxelService

Legitimate Lambda code, not malware. Let me search for the Lambda's failed executions and also for `

Root cause found: **Athena ThrottlingException** — "An error occurred (ThrottlingException) when cal

Legitimate cron config. Now I have all evidence. The cron runs at HH:31 every 4h, processes up to 30

The user note says the pipeline manages the status field, so I will NOT modify the cluster frontmatt

RCA complete. Report at `content/docs/incidents/af5f0fa7-6dda-4890-abb1-2ad1ce01d686/rca.mdx`.