Late usually means waiting, not slow
Every background job spends time in two places: waiting for its turn, and then running. On Tableau Server, background jobs such as extract refreshes, subscriptions, flows and data-driven alerts are run by the Backgrounder process, which handles one job at a time per process. When more jobs are due than there are processes free, the rest wait.
So a refresh that “takes an hour” may run for ten minutes and wait for fifty. The fix for waiting is very different from the fix for slow running.
Why jobs wait
- Everyone picks the same time. Schedules cluster at the top of the hour and just before the working day starts.
- Long jobs block short ones. A few heavy refreshes can occupy processes while many quick ones queue behind them.
- Everything shares the same queue. Subscriptions, flows and alerts compete with refreshes.
- Priorities and manual runs. Tableau orders scheduled jobs by priority, and a manual “Run now” starts ahead of scheduled work. Tableau explains the rules in How scheduled server jobs are prioritised.
What to change, in order
- Spread schedules across the night instead of stacking them at one time.
- Move the heaviest refreshes earlier so they finish before the busy window.
- Make refreshes lighter with incremental refreshes, filters and fewer fields.
- Refresh less often where the business does not need hourly data.
- Stop refreshing unused content. See retiring stale content.
- Set priorities so business-critical content goes first.
- Then add capacity, if the pattern persists, following Tableau’s guidance on the Backgrounder process.
On Tableau Cloud
Tableau Cloud runs the jobs for you, but the same scheduling habits apply, and each site has a daily refresh capacity. Tableau emails site administrators as a site approaches it, and refreshes beyond it are cancelled. See Capacity set at the site.
Check that the change worked
Compare when key refreshes finish over a few weeks before and after the change, especially on your busiest days. If waiting has dropped and content is ready before people start work, you have fixed the problem without buying anything.
Common questions
Why are my Tableau refreshes late?
Usually because jobs are waiting for a free Backgrounder process, often because many schedules run at the same time, rather than because each refresh is slow.
Should I add more backgrounder processes?
Only after spreading schedules, lightening heavy refreshes and removing unused ones. If refreshes are still late, follow Tableau’s Backgrounder guidance to add capacity.
Does this apply to Tableau Cloud?
Yes. Scheduling habits matter on Tableau Cloud too, and each site also has a daily refresh capacity.
Further reading: Tableau Help, Tableau Server Backgrounder; How scheduled server jobs are prioritised; Capacity set at the site. Tableau and Salesforce are trademarks of Salesforce, Inc.