New: MCP server monitoring is live. Start free trial
LoopsSchemaBehavioral

Response schema changed for GET /v1/workflows/{workflowId}/nodes/{nodeId} (ExperimentBranchWorkflowNode)

Affected surface
GET /v1/workflows/{workflowId}/nodes/{nodeId}
Affected field
ExperimentBranchWorkflowNode

What changed

Response schema changed for GET /v1/workflows/{workflowId}/nodes/{nodeId} (ExperimentBranchWorkflowNode) Affected surface: GET /v1/workflows/{workflowId}/nodes/{nodeId}. Root cause: schema `ExperimentBranchWorkflowNode`. Detected at Wed, 22 Jul 2026 06:06:39 UTC UTC.

Diff

{
  "path": "GET /v1/workflows/{workflowId}/nodes/{nodeId}",
  "removed_fields": [
    "experimentId",
    "experimentType",
    "url"
  ],
  "schema_path": "schema ExperimentBranchWorkflowNode"
}

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.

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.