DSR pipeline reschedule — Step 1 EXECUTED, Step 2 FAILED via non-atomic update_extract_refresh_task wrapper
Decision
Executed Plan A: (1) Fivetran SharePoint connector daily_sync_time shifted 05:00→11:00 IST via mcp__fivetran-mcp__modify_connector v19.1.2 — succeeded, verified. (2) Tableau extract refresh task reschedule (6 sales workbooks) FAILED — wrapper’s DELETE-old + CREATE-new pattern executed DELETE successfully but CREATE returned persistent 500 from Tableau Cloud, leaving 6 workbooks orphaned with no refresh task. Stopped REST recovery to avoid further damage; handed off to operator-driven recovery (Tableau Desktop overwrite-publish OR Web UI new-task-create per workbook).
Rationale
Diagnosis (high-confidence): Tableau skill gotcha #8 manifests in extract-refresh-task lifecycle — keypair-auth saved-credential binding got severed when the original task was deleted; CREATE then fails Cloud’s connection-validation but returns generic 500 instead of documented 403132. Confirmed not parallel-call concurrency (sequential retry reproduced same 500); confirmed not site-wide API issue (30 other tasks healthy via list_extract_refresh_tasks). The update_extract_refresh_task wrapper is non-atomic and unsafe for any non-password-auth workbook — every Runwal workbook on subodhrunwalgroup is keypair-bound, so this wrapper is a loaded gun for any reschedule operation. STOPPED rather than continued retrying because each REST attempt risks further state damage and the credential-binding loss is irrecoverable via REST.
Alternatives Rejected
A) Continue retrying create_extract_refresh_task — REJECTED, persistent 500, would not recover and risks further state corruption. B) Try delete_extract_refresh_task path — N/A, tasks already deleted. C) Use update_workbook_connection to re-bind credentials post-CREATE — REJECTED, can’t update connection on a workbook with no task to attach the new schedule to; also gotcha #8 explicitly flags this path as unsupported for keypair. D) Operator path via Tableau Desktop overwrite-publish OR Cloud Web UI — SELECTED as the only viable recovery; matches gotcha #8 guidance and EA Workbook Delivery Contract.
Outcome
Pending