/informes pool-acquire timeout: page fires ~24-query Promise.all (page.tsx:219-346) against deliberate pool max:2 / connectionTimeoutMillis:5s (pool.ts:11-17, WI#194 serverless conn-storm tuning). Heavy comisión (…006) drain >5s → trailing waiters throw 'timeout exceeded when trying to connect'; client echo surfaces Next digest 1177967776. Reproducible on any heavy comisión filter. Fix: bounded-concurrency wrapper on the fan-out (app/coder) and/or modest pool bump (db owns, trades vs conn-storm). 2 events/30d but reproducible.

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-13
• wi-cli-venus completed · 2026-06-14
  Root cause (db): NOT a slow query — cumulative pool-acquire wait. /informes 24-wide Promise.all starves pool max:2; 19185ms = queue time. Fix: bounded-concurrency runner N=6 on /informes + /alumnos fan-out (5f13d10, async-pool.ts), pool max:2 untouched per WI#194. + advisor-flagged practicaReviews(practicaId) FK index as hygiene (b92a8b3 / migration 023, indisvalid=t). Both audit PASS+PTD (v1.69.17/.18, READY, runtime clean). Pool 2->4 bump deferred as reversible next lever only if timeouts persist (would need WI#194-tradeoff review). Flown solo per fly-solo protocol.