You’re offline. This is a read only version of the page.
19
Hey forum,
I a struggling to solve the following issue and would appreciate any support on that topic from here:
We are running a PowerApp that triggers a flow every time the app is opened by a user. The flow connects to an excel File on SharePoint and retrieves the content of a table inside of the file.
The file on SharePoint is only a couple of KB and contains a table with 5 columns and apprx. 900 rows. The flow fails when trying to retrieve the tables in the file.
We have been using this flow for months now without any issues. But starting from Thursday last week, wee have seen a steep incline in the number of errors.
The error we are getting is this one: "The request is forbidden by Graph API. Error code is 'AccountQuotaExceeded'. Error message is 'Quota for this site has been exceeded. Changes to your data cannot be saved.'."
Indicating, that a Quota limit is reached. I don't quite understand why we are reaching a limit all the sudden, because neither the overall Flow usage nor the size of the file changed in the last months.
The flow looks like this:
The error message on te Get Tables Action is:
The flow is executed on the license of the user who started the app.
Update: While I am able to view the file on Sharepoint, I am getting the same message when trying to edit the file:
Any Idea where this could come from?
Please let me know if you need any more information to help me resolve the issue.
Thanks in advance.
We had the same issue. AccountQuotaExceeded
First I deleted all old files from the recycle bin in Sharepoint and increased the storage site limits and added a warning email for future storage issues.
https://learn.microsoft.com/en-us/sharepoint/manage-site-collection-storage-limits
Then we had to re-assign the fields in Update a row and Add a row into a Table.
Last thing was to trigger the fields that were wrong in the excel in Business Central with shipping it and unship it.
That was our solution.
Nevermind. Found the issue myself.
The Sharepoint that we were using was actually at the maximum storage capacity (something that I was not able to check myself). It seems that any incoming API calls are blocked when the storage limit is reached.
After cleaning up the Sharepoint of some unused files, the issue was resolved.
#1
WarrenBelz
146,658
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,999
Most Valuable Professional
Share
Report
All responses (
Answers (
