Is there a way to increase the request limit to greater than 50 for custom apps?
Please share the Account ID and App ID so that we will check the actual request limit for the app and get back to you
By Account ID, do you mean the domain(https://rapidodesk.freshdesk.com/) or the email address of the account? Also I couldn’t see the App ID mentioned anywhere on the freshdesk apps section. Its a custom app.
@Neil_Dahiya You can find the app ID in the URL of the app in the developer portal.
I didn’t see any request breach limit for this app
39846-webhook_caller, have you get any error from the request API?
do let us know.
@Santhosh The limit isn’t breached because we can only enable it if we’re sure that limit won’t cause requests to be dropped. Else we’ll have a data inconsistency. That’s why the app is disabled at the moment.
We need more information to investigate further,
- What is the use case of the app? Describe every flows if it has multiple flows.
- How many concurrent users / agents will be using this app?
- What is the number of request made by a single instance of the app, within a given minute (the new rate limit required)?
- What is the nature of the API calls being made from the app using $request and can any of them be cached?
- Why would you think, increasing the rate limit, would solve the problem?
Having the information, will allow us to solve your use cases better. The $request is a platform resource, and we would like to understand the usage better, before bumping up the limits.
please do let us know
- The app has just 1 flow. It makes a POST request every time a ticket gets created or updated.
- The app wouldn’t run on per user basis, rather it will run for creation/updation events for each ticket.
- The number of requests we require is 1700 per minute.
- It would be a simple POST request and they can’t be cached.
- The only problem we have right now is that requests might get dropped if the limit gets crossed. Increasing the rate-limit seems to be the only option.
Also can we get the customer satisfaction rating, closed_at, resolved_at, first_responded_at time in the ticket events data (onTicketCreate, onTicketUpdate, onConversationCreate).