Second Brain

DSR pipeline reschedule re-attempt — session-cache staleness pattern identified, distinct from server-feature gap

2 min read

DSR pipeline reschedule re-attempt — session-cache staleness pattern identified, distinct from server-feature gap

Decision

Re-flagged DSR pipeline reschedule blockage as a session-level transport cache miss, NOT an MCP server feature gap. fivetran-mcp v19.1.2 and tableau-mcp v6.0.4 are both verified live with the new tool surfaces (daily_sync_time + schedule_type on modify_connector; update_extract_refresh_task + create_extract_refresh_task on Tableau). However this Claude Code session’s deferred-tool registry was populated before container restart and holds pre-upgrade schemas. Stopped per tool-ambiguity protocol — did not bypass with curl/scripts. Path Z (fresh session) recommended; manual UI (Path X) viable fallback.

Rationale

Distinguishing the session-cache class from the server-feature class matters for future incidents — same surface symptom (tool unavailable in session), completely different remediation (operator restart vs dev MCP patch). Without this distinction logged, future agents will repeat the wrong remediation path or escalate to dev when a 30-second Desktop refresh would resolve it. One harmless validated attempt was made (nesting daily_sync_time inside config field which has additionalProperties: true) — Fivetran returned 200 OK but silently ignored the unknown nested key; connector state unchanged. Diagnosis confirmed via direct curl to /health and /mcp tools/list on both servers.

Alternatives Rejected

A. Bypass via direct curl/script (REJECTED — tool-ambiguity protocol). B. Force the tool call with daily_sync_time at top-level (REJECTED — client-side schema validator blocks additionalProperties: false). C. Delete-only Tableau path (REJECTED — would orphan all 6 sales dashboards with no recovery path in this session). D. Manual UI path X (VIABLE FALLBACK, ~7 min for AJ).

Outcome

Pending

Graph View

Backlinks