Crossing a bunch of limits and territory here. With data actions, there is a limit in campaigns that only allows you can use like 10 simultaneous campaigns running with data actions and only 2 allowed in rules per campaign, so that is a limit on Outbound not data actions on the whole.
Now, data actions can call internal or external API's, but Genesys only really cares about those or external web services hitting the Genesys APIs. Each API has their own limits like Analytics with an activity rate of 20/sec or Agentless Messaging at 300/min, so it is very hard to say there were are strict API calls per second limitations. If you want to see these, this resource is good: Limits
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.comhttps://www.ttecDigital.comhttps://RobertWC.Blogspot.com------------------------------
Original Message:
Sent: 12-17-2024 10:17
From: Shahar Leonard
Subject: Outbound Call rule Data Action limit
Hey Robert :)
Regardless of Data Actions limits,
The phrase "The maximum number of API calls from rules per second is five per pre-call and five per wrap-up." from the Outbound campaign limits - Genesys Cloud Resource Center article is not clear to me.
What is exactly "API Calls", I would guess that this is not Data Action since if it was Data Action it was written "Data Action" and not "API Calls".
So, if "API Calls" is not Data Actions, you might know what is "API Calls" in this context?
Thanks, and best regards,
------------------------------
Shahar Leonard
Technichian
Original Message:
Sent: 12-20-2022 11:20
From: Robert Wakefield-Carl
Subject: Outbound Call rule Data Action limit
Genesys does have a limit on the number of outside web services that are accessed through Data Actions at a time and over time. That is where the limit is when calling your own web service. This is there to limit race conditions when calling an outside service.
------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
https://www.Avtex.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 12-20-2022 10:42
From: Eric Berkshire
Subject: Outbound Call rule Data Action limit
I guess I'm misunderstanding where the api limit occurs here. The data action is using a webservice we own which does not have a rate limit. Is there something in the rules themselves that uses an internal api before it sends out the request that will be rate limited?
------------------------------
Eric Berkshire
Broker Solutions, Inc. DBA New American Funding
Original Message:
Sent: 12-20-2022 10:24
From: Robert Wakefield-Carl
Subject: Outbound Call rule Data Action limit
You will get the infamous 429 response if you hit API limits. You should be designing for this in your Flow or API design. The new API Performance View is great for seeing how many times you hit this.
------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
https://www.Avtex.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 12-20-2022 10:10
From: Eric Berkshire
Subject: Outbound Call rule Data Action limit
HI All,
Per the documentation, "The maximum number of API calls from rules per second is five per pre-call and five per wrap-up." Does anyone know what happens if you hit the limit? Is the 6th request scheduled for the next second? Does it throw an error? Is there anyway to increase this limit?
We have a rule that fires a data action at end of every call.
I'm worried that our current design may eventually fail at scale.
Thanks,
Eric
#Outbound
------------------------------
Eric Berkshire
Broker Solutions, Inc. DBA New American Funding
------------------------------