Changes / BI & analytics / Tableau
Packaging changelow impact
New Tableau Cloud sites default to 10 concurrent extract refreshes
From May 2026, new Tableau Cloud sites get a default of 10 concurrent extract refreshes instead of the previous 25 for qualifying sites.
Who’s affected
Admins of new Tableau Cloud sites provisioned from May 2026 (Tableau 2026.1) on Enterprise, Tableau+ or the Advanced Management add-on, especially teams running many scheduled extract refreshes at once.
Not affected: Existing Tableau Cloud sites, and teams on new sites whose refresh schedules rarely exceed 10 at the same time. Admins can also change the default.
What it costs
No price change in the record. The default drops from 25 to 10 concurrent extract refreshes, so busy refresh windows on new sites may queue and run later, which costs admin time rather than licence spend.
When to act
The change is already in effect for new sites, so check refresh schedules and the site setting before the next big refresh window or site migration.
Blast radius: Extract-based dashboards on new sites may show stale data if refreshes queue behind the 10-job limit. Delayed refreshes can also hit data-freshness SLAs and any downstream subscriptions or alerts.
What should you do? decision tree
- you created or plan to create a new Tableau Cloud site on 2026.1 or laterCheck the site's concurrent extract refresh setting in site admin and compare it to your peak number of simultaneous refreshes.
- your peak simultaneous refreshes stay at or under 10Leave the default as it is and keep watching refresh queue times.
- your peak exceeds 10 and refreshes are delayed or queuedRaise the site default, or stagger schedules so fewer refreshes start at the same time.
- you are migrating from an older site that ran with 25 concurrent refreshesSet the new site's value to match your old workload before cutting over, and test with a full refresh cycle.
- you cannot raise the limit or reduce load enoughAsk your Tableau account team to confirm what limit your edition supports and move heavy extracts to live connections or upstream scheduling.
Options
- OptimizeStagger extract schedules across the day so fewer than 10 refreshes start at the same moment.
- OptimizeSwitch to incremental refreshes and retire unused extracts to shorten run times and free up refresh slots.
- NegotiateChange the site default in admin settings, or ask your Tableau rep to confirm the limit your plan allows.
- Re-architectUse live connections for hot dashboards, or trigger refreshes from your orchestrator after upstream loads finish.
The facts straight from the source
Facts above are extracted from the source and checked word-for-word before publishing. The guidance sections are AI-assisted analysis based only on those facts: a starting point, not legal or procurement advice. Spotted an error? Tell us.
Related changes
- Amazon QuickSightAmazon QuickSight becomes Amazon Quick Suite (Quick Sight)
QuickSight is renamed Amazon Quick Suite, with the new UI and branding rolling out globally from October 9, 2025 while existing BI functionality continues.
Packaging - LookerLooker Studio is renamed Data Studio
Looker Studio is renamed Data Studio, split into a free Data Studio edition and a paid Data Studio Pro edition for scaling teams.
Packaging - TableauTableau Cloud flow resource blocks move to tenant-level allocation
Flow resource blocks are no longer auto-provisioned per site; purchased blocks are allocated at tenant level by cloud administrators from May 2026.
Packaging - TableauTableau Cloud adds capacity-based Viewer Blocks (unlimited viewers)
Tableau Cloud introduces capacity-based Viewer Blocks that replace per-user-per-month Viewer licensing, with no limit on Viewer accounts, starting July 2026.
Billing