Tableau Refresh Failure Agent with Claude Code
Working out blast radius has no shortcut: fetch the job, fetch the datasource, then query the site to find which other extracts on the same connection died in the same window. Claude Code stays reliable over a long task spanning several connected tools, and that extra sweep is what turns one failure notice into the nine datasources that actually broke.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Finance Daily Revenue
Extract refresh job 8f2c41 failed at 05:12 UTC after 41 seconds. Error: [Snowflake][ODBC] (39001) Incorrect username or password was specified. Unable to connect to the server. Scheduled daily at 05:00.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Tableau
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Escalation rules
Which dashboards the business actually watches and who to tell when they go stale - your critical projects and the teams behind them, your quiet hours, and the first check you want suggested for credential failures and timeouts.
Runs on Claude Code
Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Claude Code for this agent
The sweep is the value
One expired credential takes down every extract behind it. Checking the rest of the site before writing is an additional round of work, and a harness comfortable with long tasks actually completes it.
Who feels it comes first
The note leads with the project, the owner and the teams whose dashboards are stale, then the technical detail. Ordering a message for its reader rather than for the error takes care on every run.
Before you fork
How do we know it will find the sibling failures?
Expired Credential is the staged failure to watch, because a Snowflake password error is exactly the kind that hits every datasource behind one connection. A correct run reports a count with two or three names in the FAILED section rather than the single job it was handed. If it reports one, it skipped the site query and you have caught that before a real morning.
Run it with a different agent
Put Tableau Refresh Failure Agent to work on Claude Code
Free to start. Guided setup, a test run against staged conversations, and it's live.