Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.
I'm receiving this error qhen I try to refresh my dataset
this dataset is conected to and ODBC Presto
Any workarround for this
Hi @Anonymous
Thanks for reaching out to us.
>> query error max requests queued per destination 1024 exceeded for
Normally this error is a symptom of another problem. The symptom is that HTTP request start taking longer, connections are used longer (HTTP 1 is pipelined, not multiplexed), the connection pool fills up, and then request queue until you hit the limit. The thing to look at is why are connections taking longer than normal? I’d start by upgrading to the latest release as we are working on fixing some bugs that causes longer request times. After that, I’d look at the workers to see if they are doing long full GCs. This is normally the case, and it is normally causes by over committing the cluster resources (too many concurrent large queries). The other possible cause, you could be overloading the network between your nodes.
From: Max requests per destination 1024 exceeded for HttpDestination (google.com)
Best Regards,
Community Support Team _Tang
If this post helps, please consider Accept it as the solution to help the other members find it more quickly.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.