Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I have a Custom Connector that is working well. It pulls data, handles pagination, and handles the Access Token expiring after 15 minutes during large calls. However, I have an issue specifically with Power BI Online and using Data Gateways. When I refresh in Power BI Desktop, I can make large calls and rely on the pagination and refresh of the Access Token after 15 minutes. However, Power BI Online behaves differently. Power BI Online will start by Refreshing the tokens (as expected), then it will grab data and paginate for 15 minutes (all as expected). After 15 minutes, it hits 401 Unauthorized errors as the Access Token has expired (once again, still working as designed). Where Power BI Desktop is smart enough to just run the Refresh function and continue where it left off, I can see that Power BI Online never attempts to run the Refresh function. Instead, it just fails the query and returns the Invalid User Credential error.
Has anyone ran into this issue before? All testing, debugging, and even live environment using Power BI Desktop work fine along with any queries using Power BI Online that happen to be under the 15 minute expiration time. It's only the detection and use of the Refresh function in the middle of queries that is having an issue. I have found this issue is for both the Personal Data Gateway and the Enterprise Data Gateway.
Solved! Go to Solution.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
9 | |
8 | |
4 | |
2 | |
2 |
User | Count |
---|---|
4 | |
3 | |
3 | |
3 | |
2 |