The seven errors every Tableau extension throws

First, the thing nobody tells you: errors are step three, not failure. Building an extension is a loop: write it, load it in Tableau, read the error, fix, reload. One or two cycles to clear is normal even when you know what you're doing. If you're pasting an error into an AI assistant, paste the exact text; these messages are terse but they are specific, and the specificity is the only thing that makes them fixable.

01 · My manifest change did nothing

This one is worth internalising early, because it disguises itself as every other error on this list. You'll fix a genuine manifest bug, see the identical failure, and conclude the fix didn't work, when actually Tableau never read it.

02 · It loads, but it's blank

The deeper fix is to make this error impossible to see. An extension that renders nothing when its inputs are missing is indistinguishable from an extension that's broken: by you, and by every colleague who opens the workbook later. Always render a real empty state:

// Not a blank box, a sentence that says what to do.
if (!worksheet || !measures.length) {
  show('Add a worksheet with a measure to this dashboard');
  return;
}

Ten seconds of work that converts a support conversation into something the user fixes themselves.

03 · "Missing XML element"

Order genuinely matters: the schema is a sequence, not a set. A manifest with every required element in the wrong order fails exactly like one that's missing an element. The full anatomy is here.

04 · It won't load at all, just spins

This one cost me seventy minutes during a live build. There is no error message anywhere in the chain (not in Tableau, not in the terminal) because from Tableau's point of view nothing has gone wrong yet. It's still waiting.

The reliable habit: before debugging anything else, open the manifest's URL in a plain browser tab. If your extension doesn't render there, it will never render in Tableau, and the problem is in your server, not your extension.

05 · Data reads empty when there's clearly data

// Breaks the moment someone reorders the pills.
const total = rows.reduce((a, r) => a + r[2].nativeValue, 0);

// Survives it.
const m = table.columns.find(c => c.dataType === 'float' || c.dataType === 'int');
const total = rows.reduce((a, r) => a + r[m.index].nativeValue, 0);

06 · FD722608: the content-model error

  <source-location>
    <url>https://your-host.example.com/index.html</url>
  </source-location>
  <icon/>   <!-- this line. this is the whole fix. -->
</dashboard-extension>

Learning to read that error message is worth more than the fix itself, because the same code covers a whole family of problems. The parenthesised list is the schema: elements in required order, a ? marking the optional ones. Whatever's in that list and missing from your file is your answer.

Building a viz extension? FD722608 has a second, nastier cause there: an encoding-icon token that isn't in Tableau's enumeration. The published docs list tokens that the parser rejects, and it reports only the first bad one, so you fix and re-fail several times over. More on viz extensions here.

07 · Fine on desktop, broken once published

One related non-bug, because people file it as one: extensions don't render in PDF exports or printed images on Server and Cloud. Blank space where the extension was is expected behavior, not something you can fix in your code.

When to stop fixing and start over

If you're three iterations deep on the same error with no movement, rewriting that piece from a clean prompt is nearly always faster than a fourth patch. State the goal, the field setup, and what's failing, and let it regenerate. Patching a misunderstanding just layers more code on top of it.

Or skip the whole catalog: these seven fixes (and the viz-extension ones) are baked into a free SKILL.md your coding agent reads before it writes a line, so the errors mostly never happen. Emailed to you, free.