Hello team we are having the following problem in production, but we don’t know the reason, the queries to obtain the information are well-structured, and we don’t have more than three matches with the query.where. We would be very grateful if you could help us with information to fix this error.
ERROR 2023-08-30T22:32:15.231Z 8.1.0 ari:cloud:jira::site/f152325e-3b50-4055-943c-0fefd8f87c37 0921cce3-db7a-4ea9-aa45-a30dbdb2adef resolver core:function {"message":"You are trying to access 'appStoredEntities' too often","name":"FUNCTION_ERR","stack":"Error: You are trying to access 'appStoredEntities' too often\n at Function.forErrorCode (index.js:31721:16)\n at assertNoErrors (index.js:31744:33)\n at getResponseBody (index.js:31759:5)\n at async GlobalStorage.query (index.js:31824:16)\n at async GlobalStorage.list (index.js:31781:26)\n at async getDelegations (index.js:50291:19)\n at async getAllDelegations (index.js:50265:18)\n at async validateDelegations (index.js:50357:26)\n at async resolve (index.js:31650:28)"}```
I think your app is exceeding the Forge storage limit of 200 queries per 20 second interval. Unfortunately, this limit doesn’t increase based on the number of seats (users) like some other limits do, so I suspect solving this may be difficult if the queries are triggered from user interactions.
I think it would be worthwhile raising an issue in the FRGE project, explaining your scenario. The Forge team may be able to make the limits scale by seats.
Thanks for the answer, I don’t think that’s the problem, because the client has told us that he has nothing created with the key that represents the method. And we have analyzed our code, and we have declared correctly the methods to access the storage. And yet it’s a bug that we can’t replicate in our test and development instances. If you have any idea what could be happening, or if you see the need for me to contact the forge team for a more precise answer, I would be very grateful.