You have exceeded the amount of requests allowed in the current time frame and further requests will

[Jean_Jales]

I receive this message when i do a post at https://api.powerbi.com/v1.0/myorg/groups/{{Workspace}}/datasets/{{DatasetId}}/refreshes

even when i wait for 2 days i still got this message, before that day i used to use this endpoint to refresh an dataset, I'm a PRO user. What exactly is limitating my usage?

[v-pnaroju-msft]

Thankyou, @GilbertQ, @tayloramy and @pbiuseruk for your responses.

Hi Jean_Jales,

We appreciate your inquiry via the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solutions provided by @pbiuseruk and @tayloramy to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[tayloramy · Accepted solution]

Hi @Jean_Jales, 

Is your workspace a pro workspace or are you a pro license holder using a premium workspace backed by a capacity? 

For pro workspaces, only 8 refreshes a day is allowed: https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/refresh-dataset-in-group

Can you share a screenshot of the refresh history for this semantic model? And then as @GilbertQ asked, a full error message that you are getting would also be helpful. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[Jean_Jales]

its a Pro workspace, i shared the printscreen beyond the other replies. My refreshes now are working normally, but i'm still worried about what happened

[tayloramy]

Hi @Jean_Jales , 

What is the payload you are sending? 
Are you trying to do an enhanced refresh by chance? Those are only supported on fabric capacities (and premium, but those are end of life now) 

https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/refresh-dataset

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[GilbertQ]

Hi @Jean_Jales 

What happens if you got into your semantic model and click on the Refresh Now button? That should allow you to refresh it manually. Also, if you are getting an error message, could you please post it so we can help you diagnose it further?

[Jean_Jales]

The semantic model button works fine, but the problem is the use of the api that gives me this error in any enviroment (postmans, codebase). As I mentioned, it worked before, but suddently the errors popup in the body.

[pbiuseruk]

Based on this message - double check that you haven't made some code somewhere else, that's calling the service too many times. 

If you come across issues like this, I sometimes make a new workspace and just pull that same report in and then test it. This can help rule out a fair amount of things as part of your troubleshooting process.

[pbiuseruk]

Hi @Jean_Jales ,

Pro workspaces are limited to having 8 scheduled refreshes per day. If you've already got 8 scheduled refreshes and it's happened 8 times, then you're calling that API - it could be that's the reason you're getting the error message.

Also worth checking the type of the workspace to ensure it is a Pro workspace.

Lastly, you could try using the Refresh Dataset action in Power Automate to trigger your refreshes. This could be done on a schedule or on demand.

Please let me know if that helps.

[Jean_Jales]

The workspace is a PRO licence, the way i make the requests are just by my codebase or postmans, it's not based on schedules, the ideia is to when clicked in the web, calls my backend and triggers the dataset to be refreshed. 

Use PowerAutomate for this purpuse is tricky because an common user could not see Power Automate buttons, unless i use User Owns Data embed, but it requires the user to have access to an acount.

[pbiuseruk]

That makes sense - if you're worried about running into the same issue again, I'd probably make a fallback mechanism that relies on the Power Automate method. There are potentially some ways around what you said (but this is a very convoluted solution I'm just thinking off on the fly). You could make it so that the user clicks your button to refresh and it checks the response (assuming you have something that does automatic retries already). If the retry fails 3 times, then it sends a generic mail to a certain mailbox in a specific format. You make a Power Automate flow that's triggered on that email to go and refresh the report.

The whole idea of this is just to provide a fallback mechanism to try it in another way automatically. You shouldn't have any issues in regards to the Power Automate ownership if implementing in this way.

Hope that helps.

Also, if you're worried about out of date data, it would make sense to include the date/timestamp on the report so users can see when it was last refreshed.