Genesys Cloud - Developer Community!

Hello,

Need to call an external API on every a Dialer call (progressive/ Predictive) and based on the result need to update the pre-call rule to either to call or Reject the contact.

I see the  "actions.concurrent.executions.max"  limit as 50 and set as a configurable parameter but need to know the max limit that can be set to see if the above design is viable. 

Thanks

Rahul

Hi Rahul, I believe this informations isn't publicly available.

At least I have never seen any documentations that would provide the maximum value that those limits can be set to.

Through here your best hope would probably be someone who has set this specific limit to a higher value in the past, they would be able to confirm what was used on their case.

But I think the best approach would be for you to open a case, they can probably confirm to you there the maximum value that this can be changed to.

Hello Rahul,

50 is the default max limit for this parameter. As far as I remember, it can be increased to 75. You can raise a case with support to increase it for your org.

Hi Rahu,

You can check the official documentation here:

https://developer.genesys.cloud/organization/organization/limits#data-actions

https://help.genesys.cloud/articles/data-actions-integration-performance-analysis/

Genesys lists actions.concurrent.executions.max as one of the limits related to Data Actions. This limit controls how many Data Actions can be executing at the same time in the org. The documentation also explains that longer-running Data Actions consume concurrency slots for longer, so endpoint latency is very important in this type of design.

If the external API is slow or the campaign volume is high, you could start hitting concurrency rate limit errors.

About the maximum value that can be configured, I would recommend opening a case with Genesys Customer Care to request a limit review/increase.

Hi @Rahul Mohanakumaran

Open a case with customer care, asking your questions. Usually, in my experience, customer care share with us the limits of configurable options and the conditions to increase the current ones.

Regards,

SG

Hi Rahul,

I would be careful with this design if the Data Action needs to run on every Progressive/Predictive Dialer call.

The actions.concurrent.executions.max limit controls how many Data Actions can run at the same time in the org. If the limit is 50 and your external API takes a few seconds to respond, a high-volume campaign can reach this limit quickly, causing additional executions to fail or be rejected.

The viability depends on:

• Dialing rate / calls per minute
• External API response time
• Number of campaigns running
• Other flows also using Data Actions
• Timeout and retry behavior

For this use case, I would first validate the expected volume and run a load test. If the API must be checked for every contact, a better approach may be to pre-process or enrich the contact list before dialing, instead of calling the API in real time for every dial attempt.