Short scheduled runs are waiting behind long warehouse jobs in the same worker pool.
Reporting deadlines need predictable starts while long transformations still need capacity to finish.
Who you’d be doing this for
“Finance asked why the dashboard was stale again, and all I had was a run still waiting in queue.”
Yaa Diop · Analytics Engineer
Owns scheduled dbt models that publish finance and operations datasets for a large Enterprise customer.
What is at stake
Scheduled reporting runs are waiting more than 20 minutes when long Snowflake jobs fill the shared worker pool. You must weigh predictable reporting starts against throughput for long-running transformations.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- reporting-window reliability vs long-run throughput
- queue fairness vs worker utilization
- fast mitigation vs durable scheduler behavior
- automated test generation vs reviewed coverage
Why Fivetran
The scheduler and execution harness determine whether dbt projects reach downstream reporting windows when shared compute is under load.
Written with these in mind
Not your kind of problem? 43 more at Fivetran, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.