Tableau Feed

Hi Erik, 

That error message actually tells you the real problem: Tableau Server's response is sending two different X-Frame-Options headers

— one DENY and one SAMEORIGIN — and browsers block the frame completely when they see conflicting values like that. 

Likely cause: Tableau Server adds SAMEORIGIN by default. Something else in front of it — a proxy, load balancer, or WAF — is probably now also

adding DENY. Since this used to work, something likely changed recently on one of those layers (a Tableau upgrade/restart, or a new security rule). 

Quick way to check:

Look at the response headers in your browser's dev tools (Network tab) or run curl -I on the URL, and see how many X-Frame-Options headers come back. 

Fix: Only one layer should set this header — work with your network/security team to remove the duplicate. If needed, you can turn off Tableau's own header with:

tsm configuration set -k wgserver.clickjack_defense.enabled -v false
tsm pending-changes apply

One more thing worth knowing: since Salesforce and Tableau Server are different domains, SAMEORIGIN won't actually allow the embed anyway. The proper long-term fix is a Content-Security-Policy: frame-ancestors header that explicitly allows your Salesforce domain — X-Frame-Options can't do that kind of allowlisting. 

Hope that helps point you in the right direction!

Hi Kiran,

This looks like an Azure AD (Entra ID) OAuth refresh token issue, not a config mistake on your end. 

Why:

Tableau doesn't yet support single-use/rotating refresh tokens for Azure/Entra ID OAuth connections. If your tenant enforces token rotation (via Conditional Access, sign-in frequency, or CAE), Tableau's stored refresh token gets invalidated quickly — so scheduled refreshes fail even though a manual connection test succeeds (the test can trigger a fresh token; the stored one for scheduled runs can't). 

Desktop works vs. Cloud fails:

Desktop re-authenticates interactively each time. Cloud relies on a stored token for unattended scheduled runs — if that token's been rotated out, it breaks. 

Check these:

1. Azure AD Conditional Access — sign-in frequency, CAE, or refresh token rotation on this app registration
2. Whether a dedicated OAuth client is registered for Tableau in Azure AD (vs. the default shared one) — recommended for scheduled refreshes
3. Re-save credentials directly on the data source's Edit Connection page, not just Account Settings
4. Consider a service account instead of a personal identity — less exposed to MFA/session policies
5. Does it fail immediately or after a set time? A short window points strongly to a Conditional Access session policy

Fastest next step: check Settings → OAuth Clients in Tableau Cloud to see if a dedicated Azure AD client is set up.

Hi Danh, 

Good catch mentioning the MIN(0) workaround — that's likely the real cause here, not a Server bug. 

Why it happens: With MIN(0), the subtitle is just a text label on a hidden dummy mark, not a true axis property. If a filter or RLS reduces the data for that pane to zero rows (or the underlying calc returns NULL), Tableau simply has nothing to plot — so the label silently disappears. Your main title stays because it's likely a straight parameter reference, not dependent on a mark being drawn.

Common triggers:

• The subtitle calc (Actual/Prior/Growth) returns NULL once rows are filtered/RLS-restricted
• RLS often behaves like a context filter, which can affect even FIXED LOD calcs
• "Growth" especially needs a prior period — if that period gets filtered out, there's nothing to compare

How to confirm:

Reproduce the same filter/RLS condition in Desktop. If the subtitle disappears there too, it confirms it's a data issue, not a Server rendering bug. 

Fixes to try:

1. Wrap the subtitle calc in ZN()/IFNULL() so it always returns a value
2. Check if your filters/RLS are set as context filters — this can break FIXED LOD assumptions
3. Make sure the field driving the MIN(0) mark always has at least one row, regardless of filter/RLS state
4. Alternatively, skip MIN(0) and insert the calculated field directly into the worksheet title — titles aren't tied to marks being drawn, so this failure mode goes away entirely

Try it in Desktop first — that'll tell you which fix is needed.

Hello @Etsuro Tabata.  

I'm sorry, I should have commented on this before, but after a few hours, the error message stopped popping up, and I could edit my visualizations again. Also, I wasn't using Tableau Desktop, as I was using the Tableau Public website to make visualizations. Thank you for answering though! 

Nicky

Hi, @Yemi KEHINDE

This is a workaround suggested by another user.  

However, I'd also recommend reviewing the following article before deciding whether to use this approach.  

Depending on how you intend to use the workbook afterward, the licensing and sharing limitations of Tableau Desktop Free Edition may be relevant.  

<salesforce article> 

https://help.salesforce.com/s/articleView?id=005316652&type=1

@Himal Singh

Unfortunately, there is no way to do everything. 

There is an embedded license optimized for public sites, but you’ll need to set it up as a separate site from your existing Tableau Cloud site, and you’ll have to manually copy your existing workbooks and data sources. 

Please refer to the URL below.