Changes / BI & analytics / Tableau
Packaging changelow impact
Tableau 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.
Who’s affected
Tableau Cloud customers on multi-site tenants who run Tableau Prep flows on the server and have purchased flow resource blocks. Cloud administrators now allocate purchased blocks to sites themselves.
Not affected: Customers who don't run flows on Tableau Cloud, and single-site tenants, where allocation is straightforward.
What it costs
The record shows no price change; this is a packaging and administration change. The cost driver is how many blocks you hold versus how many each site actually needs, since each site keeps one default block that cannot be moved.
When to act
The change is already in effect (May 2026), so a quick audit of block allocation per site avoids stalled or unscheduled flows.
Blast radius: Scheduled Tableau Prep flows on sites without allocated blocks may not run, which can leave downstream extracts and dashboards stale.
What should you do? decision tree
- you have a single site or don't run flows on Tableau CloudNo action needed beyond confirming flows still run as before.
- you have multiple sites and run scheduled flowsAsk a cloud admin to list purchased blocks and which site each flow runs on, then allocate blocks at the tenant level to the sites that need them.
- A site has flows failing or queued after May 2026Check that site's allocation first; reallocate purchased blocks to it, remembering the default block cannot be moved elsewhere.
- your blocks exceed what sites use, or demand is uneven across sitesReview the quantity at your next renewal and discuss right-sizing with your account rep.
- none of the above resolves itOpen a support case with Tableau citing the 2026.1 tenant-level allocation change.
Options
- OptimizeAudit flow schedules per site and allocate purchased blocks to match actual demand.
- OptimizeConsolidate flows onto fewer sites so blocks aren't stranded behind the per-site default.
- NegotiateAt renewal, right-size block quantity based on measured usage across sites.
- Re-architectMove heavy data prep upstream into your warehouse or dbt to reduce reliance on Prep flow capacity.
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 - TableauNew 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.
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