New: MCP server monitoring is live. Start free
StatsigSchemaBehavioral

Response schema changed for GET /console/v1/experiments/{id}/pulse_load_history (PulseLoadHistoryDto)

Affected surface
GET /console/v1/experiments/{id}/pulse_load_history
Affected field
PulseLoadHistoryDto

What changed

Response schema changed for GET /console/v1/experiments/{id}/pulse_load_history (PulseLoadHistoryDto) Affected surface: GET /console/v1/experiments/{id}/pulse_load_history. Root cause: schema `PulseLoadHistoryDto`. Detected at Mon, 27 Apr 2026 18:36:39 UTC UTC.

Diff

{
  "path": "GET /console/v1/experiments/{id}/pulse_load_history",
  "removed_fields": [
    "dagID"
  ],
  "schema_path": "schema PulseLoadHistoryDto"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Diff your serializers against the new schema. The diff above shows what moved.

Related changes

Other endpoints affected by the same root cause.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.