Video | Tableau | Tool strategy | Productivity

Track bugs and Known issues in Tableau | Tableau KB (Knowledge base)

If something should work in Tableau but doesn't, the Known Issues page is the first place I check before blaming my data.

Watch on YouTube
  • Tableau releases monthly patches for current and older versions, so always check you're on the latest patch for your release before troubleshooting
  • Bug and release information has moved from the Tableau Desktop download page to the Salesforce Known Issues page, which opens pre-filtered
  • The status filter set to 'Solution deployed' shows issues that have actually shipped, and sorting by updated date surfaces the most recent fixes
  • Each issue lists the 'found in release' version as a floor, plus a workaround and steps to reproduce
  • You can track in-review issues, hit 'report' to flag you're affected, and get alerted with metadata when a fix lands

Tableau's bug and release information has moved off the download page to a separate Salesforce Known Issues page, and knowing how to filter and use that page properly means you can quickly check whether a problem is a known bug before you waste time troubleshooting your own setup.

Tim starts on the Tableau Desktop download page checking for the latest patch, then follows the link through to the Known Issues page where release and bug information now actually lives.

The Breakdown
  1. Check you're on the latest patch first 0:14

    Tableau releases monthly patches for the current release and continues patching older versions too, sometimes with limited support windows. Before troubleshooting anything, check the download page and make sure you're at least on the latest patch for whatever version you're using.

  2. Follow the link to the Known Issues page 1:39

    Clicking through from the download page now sends you to a separate Salesforce Known Issues page rather than showing release info in the same place. It arrives pre-filtered, but not usefully — you need to set the product filter yourself.

  3. Filter down to your specific product 2:03

    The product filter is additive, so picking a broad category first and then narrowing (for example to a specific desktop product) can leave stray labels in the filter. Remove the broader label so only your exact product remains, otherwise the list stays cluttered.

  4. Filter by 'Solution deployed' to see shipped fixes 2:20

    Setting the status filter to 'Solution deployed' shows only issues that have actually been fixed and released, rather than ones still being investigated. Sort by updated date so the most recent fixes surface at the top.

  5. Read the 'found in release' as a floor, not a ceiling 3:02

    Each fixed issue lists a 'found in release' version, but that's the minimum version the fix applies to — the fix generally carries forward into everything released since. Don't assume a fix only applies to that one exact version.

  6. Check in-review issues to confirm you're not alone 3:42

    If something's broken for you, search the in-review list to see if Tableau is already aware of it before assuming it's your data or setup. Each issue gives extra context when you open it.

  7. Use workarounds and repro steps while you wait 4:20

    Issues typically include a workaround and steps to reproduce the problem. Tim's own habit is to check this page first when something that should work doesn't, and only continue troubleshooting his data, network or Tableau setup if nothing turns up here.

Worth Knowing
  • The move to the Salesforce page means release notes and bug tracking are no longer on the same page as the download, which Tim finds a frustrating, disjointed experience
  • The product filter is additive rather than replacing previous selections, so you can end up with unintended combined filters if you don't clean up as you go
  • Some older or specific releases may not show updates beyond a certain point, so the list isn't necessarily complete for very old versions
Use It When

Reach for this whenever something in Tableau should clearly work but doesn't — check the Known Issues page before you start blaming your data, network or configuration.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.