#Tableau Cloud63 人正在讨论

 This sounds like a permissions sync issue between Tableau Cloud and the identity provider rather than an actual MFA bug, admin role changes sometimes don't propagate cleanly to Salesforce Authenticator right away. Worth checking if your site admin can fully deprovision and reprovision your user account rather than just resetting MFA, since a fresh account sync often resolves auth method conflicts like this. For getting past the AI agent, try typing something like "escalate to human agent" directly or use the phone support line if your org has one, that usually bypasses the bot loop faster than the chat widget. 

Hi , 

I think the SSO authentication is failing. 

Resolution Steps 

1. Sign out completely from Tableau Cloud 

2. Close the browser 

3. Open the browser in Incognito/Private mode 

4. Log in again using the Tableau Cloud site URL 

5. Log in to your company's SSO portal (e.g., Azure AD, Okta) first, then access Tableau Cloud 

Update / likely root cause found 

For anyone following this thread, here's where things stand. 

Symptom recap: 

- Scheduled extract refresh failed with: "TableauRuntimeException: Missing password. Incorrect username or password" (offline mode, status code 10000). 

- Test Connection succeeded every time. 

- Manually triggering a refresh from the Data Sources tab in Tableau Cloud succeeded every time. 

- Deleting and recreating the refresh schedule/task didn't help. 

- Re-entering and re-embedding the password via the web UI showed as "Embedded in connection," but the scheduled/background job still failed with the same error. 

What we found: 

We opened the workbook in Tableau Desktop and went through Server > Publish Workbook > Data Sources > Edit, checking each embedded connection's Authentication setting individually. One connection (a custom SQL connection) was configured differently from the others — it did not have "Allow refresh access" (or "Embed password") selected under Authentication, unlike the rest of the data sources in the workbook, which all had one of those two options properly set. 

What we did: 

1. Set the Authentication option to "Allow refresh access" for that connection in the publish dialog. 

2. Verified the settings for all other embedded connections as a sanity check. 

3. Republished the workbook from Tableau Desktop, overwriting the existing published workbook. 

4. Ran a full manual extract refresh from Tableau Cloud afterward — it succeeded. 

Caveat: manual/interactive refresh succeeding was already true before this fix too, so it's not fully conclusive on its own. The real test is whether the next scheduled (unattended) refresh — run by the Backgrounder/scheduler with no interactive session — succeeds. If it does, that would confirm the missing "Allow refresh access"/"Embed password" authentication setting on that one connection was the actual root cause (the other connections had it set correctly, which is presumably why they always refreshed fine). If the scheduled refresh still fails with the same "missing password" error, we'll need to dig further into differences between the manual and Backgrounder/scheduler execution context specifically. 

Will report back once the next scheduled run has completed. Posting this in case it helps anyone hitting the same "test/manual refresh OK, scheduled job fails on missing password" pattern — worth double-checking the Authentication setting per-connection in the Desktop publish dialog, not just the post-publish credential edit in the web UI.

To access Tableau Cloud Manager (TCM) without knowing who holds the admin credentials, follow these diagnostic steps to identify your site admin.

Step 1:Log in to Tableau Cloud ([https://online.tableau.com](https://online.tableau.com)).

Step 2:Go to the Users tab from the left sidebar navigation.

Step 3:Look at the Site Role column.

Step 4:Filter or search for users marked as Site Administrator Creator or Site Administrator Explorer.

Contact those individuals—in many organizations, the Site Administrator is also the Cloud Administrator (TCM Admin) or knows who made the original procurement purchase. 

@DIEGO FERNANDO MARTINEZ RODRIGUEZ

I'm trying to save the snowflake keypair credentials under "Saved Credentials for Data Sources", when i enter the server URL its showing a caution as "Invalid Server".  

Actually the same server "URL" is working fine when i embedded the credentials in tableau desktop and even tried publishing to tableau cloud and extract refresh is also working fine for the embedded credentials.   

Main issue is, i have a workbook in tableau cloud which is live connection for that i need to use the saved credentials. followed the same format

Confused why credentials work fine when embedded with extracts and not as saved credentials. 

Another important observation is, I'm not having any issue with on-premises tableau server, i could save the same keypair credentials without any issue. 

Hi Monika,

Sometimes when you convert from normal view to mobile view the filters will only operate on the original normal view - I've never done enough research into the specific reason why this happens but you can confirm this by using the filter and switching back to the normal view - it should have applied on that screen, but doesn't on the mobile view.

To get around this, just delete the filter, then in the mobile view re-expose the filter which you know will apply to that sheet, and it will work just like the original should have. Technically this is 2 separate filters, but I doubt your usecase will have users that dynamically switch between mobile and desktop views (its a very rare event and F5 refresh will fix it).

HTH

Peter

Custom views are fragile but they do not inherently break whenever you update your workbook. If you delete the workbook first it will delete all custom views but if you overwrite they will be preserved. I have been supporting custom views for 15 years on Server and Cloud. Significant changes to the workbook data sources or views are likely to break the custom views but small changes should not. 

This may not help the original poster "move to a new environment" but I wanted to clarify.

Hi Jay, 

Performance Recording is available in Tableau Cloud — it's just configured differently than Desktop (site-level admin setting + URL parameter, not a menu toggle): 

1. As a Server/Site Admin, go to your Tableau Cloud site's Settings. 

2. Under Workbook Performance Metrics, check Record workbook performance metrics, then Save. 

3. Open the view you want to diagnose. 

4. In the URL, add :record_performance=yes& immediately before the session ID (:iid=...). Example: 

5. Interact with the view as needed, then click the "See performance recording data" icon (or link) that appears to open the generated performance workbook. 

This is the same underlying feature as Desktop, just enabled per-site rather than via a Help menu toggle — the doc you linked is specifically the Desktop version; the Server/Cloud version is here: 

Reference:

If you don't see the site setting, you may not have Site/Server Admin rights — that setting is admin-only, not available to regular Creator/Explorer roles.

@Bob Haffner

Unfortunatelly, the only way to set key pair credentials for Snowflake is using Tableau Desktop and publishing the datasource to Tableau Cloud. 

Thus, you have two options: 

a. You may preserve the ownership of the user who publishes the datasource/workbook and give the refresh extract permission to other users. (yeah there is a recently new permission for this) 

b. The new owner, using Tableau Desktop, may need to connect to the published datasource, create a local copy, and publish again the datasource using the key pair stored under their user. 

I would also recommend to look and upvote ideas already created in salesforce idea forum: 

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador