Large Payload Regression

A deploy shipped a response change that now returns full nested related records instead of lightweight references on a widely used endpoint. Clients still need the data this endpoint provides, and the endpoint cannot simply be turned off — but every response is now carrying far more data than it used to, and callers that depend on specific fields in the response must keep receiving them correctly, not a silently incomplete version of them. Diagnose why response size, memory pressure, and tail latency are climbing together, and bring the API tier back to a durable, sustainable state.

Difficulty

Senior

Expected Time

~15 min

Category

API & Traffic