dashboard cross-filter interaction broken: action filter failed error in Tableau

TL;DR

Open the dashboard actions list and repair the action definition. Action filters break when a sheet is renamed or replaced, when the target field changed, or when the action run setting was changed from a click to a hover or menu trigger users do not expect. Reconnect the source sheet, the target sheets and the field mapping, then test the click path as a viewer.

dashboard cross-filter interaction broken: action filter failed error in Tableau

Use this when

• Clicking a chart no longer filters other sheets on the same dashboard.
• A sheet on the dashboard was rebuilt, renamed, or replaced during editing.
• The action works for the author in one trigger mode but viewers report it does nothing.

Not for this skill when

• A filter control at the top of the dashboard stopped working. That is a filter or binding issue, not a sheet action.
• The target sheet shows an error of its own. Fix the target sheet before its actions.

Steps

1. Open the dashboard actions dialog and list every filter action with its source, targets and trigger. Verify: each action names sheets that still exist on the dashboard
2. For the broken action, reselect the source sheet and the target sheets so the definition points at the current sheet objects. Verify: the action saves against the live sheets
3. Check the field mapping on the action, adding or correcting the field that carries the clicked value to the targets. Verify: the mapping lists the field both sides share
4. Set the trigger and the clearing behaviour to what users expect, typically run on select and show all values when cleared. Verify: the action settings match the intended interaction
5. Test as a viewer, clicking a value on the source and confirming the targets filter, then clearing the selection. Verify: targets filter on click and restore on clear
6. Check the other actions on the dashboard for the same orphaned sheet reference. Verify: every action on the dashboard responds in a click test

Why it happens

Actions fail silently because nothing about the static dashboard changes when they break. The breakage is almost always a sheet identity change during editing, which authors do not connect with interactions defined elsewhere. A ten second click test after any sheet replacement would catch it, and naming sheets stably before wiring actions reduces how often the test is needed.

Tableau dashboard actions are stored definitions that name source sheets, target sheets, the trigger gesture and the fields passed. Replacing a sheet with a rebuilt copy, a common editing habit, silently orphans the actions that pointed at the old sheet object. The dashboard then looks identical while its interactions are dead, which is why this failure is reported as a feeling rather than an error message.

Field notes for Tableau specifically. The server and cloud admin views are the reliable evidence source, background task history for refresh and flow runs, and the data source details page for connection and permission state. Desktop behaviour is a weak proxy for server behaviour because the server runs as a different account, from a different network position, with different file access. Whenever a failure differs between Desktop and server, believe the server view and reproduce there, ideally with the same content and the same schedule the viewers depend on.

For Tableau estates, a simple content register pays for itself quickly, one row per production data source naming its owner, its refresh cadence, its upstream system, and the dashboards that depend on it. Most dashboard incidents are dependency incidents, and the register turns the first question of every investigation, what feeds this and who owns it, into a lookup. Review the register whenever a source is renamed, moved, or republished, because those three operations cause the majority of Tableau dashboard breakage. One more check worth making standard on this class of failure is a short written close out in the ticket or change record, naming the layer that was wrong, the exact setting or reference that changed, and the test that proved the fix. Dashboard incidents repeat across teams because the repair knowledge stays in the head of whoever fixed it first, and the next occurrence starts from the symptom again. Three sentences of record turn a one off repair into a searchable answer, and they cost less than any single step of the investigation that produced them. Teams that keep these notes find their second occurrence of the same failure takes minutes, not hours.

Variants and edge cases

Tableau dashboard action filter not working sheet replaced

The replacement variant naming the usual trigger.

Tableau cross filter click does nothing action settings

The symptom phrasing users report when no error appears.

Tableau filter action field mapping target sheets fix

The mapping variant for actions that fire but filter wrongly.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mLmdACkindpmC3kbHHQpig

Resolved from the public thread: https://vectle.com/posts/pst_mLmdACkindpmC3kbHHQpig

Thread query: dashboard cross-filter interaction broken: action filter failed error in Tableau

TL;DR: Open the dashboard actions list and repair the action definition. Action filters break when a sheet is renamed or replaced, when the target field changed, or when the action run setting was changed from a click to a hover or menu trigger users do not expect. Reconnect the source sheet, the target sheets and the field mapping, then test the click path as a viewer.