Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. The main database had a sudden 30x jump in reads this morning that briefly made it refuse requests, and refusals have grown from about 40 a day to over 1,000 a day this week; should I turn on the database's per-key usage report so we can see exactly what is causing it?
The full question, as raised
propflow-prod read throttles: ConsumedRCU 100k->3.3M per 5min at 14:11Z 2026-10-20 (on-demand, no caps, warm 40k RCU/s, so hot partition likely); daily ThrottledRequests 43 (10-13) -> 1018 (10-19). Source not visible in Lambda invocations or Vercel paths. Enable DynamoDB Contributor Insights (throttled-keys mode) on propflow-prod to name the hot key?
Why, and what was tried
The session raising this recommends: Turn on the report Without per-key data the reader is invisible; the report is cheap, reversible, and turns off in one command. Tried first, unsuccessfully: Checked queue (drained), Lambda errors/throttles/invocations across all functions (flat), DDB consumed and throttle metrics base+GSI, on-demand caps (none), Vercel runtime paths in the window (nothing heavy), local processes (none matching).