Nope, I was just curious. It seems like there are some pretty strict boundaries around everything else for Dialer, so I was just wondering.
On a side note, I recently noticed on the limits page that there are 15 concurrent data actions per organization (which is configurable, which is good).. Couple of questions..
Is this a fairly new limit? I've never seen this before.
How would this affect a dialer campaign pre-call rule that is configured to execute a data action? Say I'm a dialer shop and I have 30 agents on-queue and I start my campaign, which has 1000 records. If I am using a progressive campaign, the campaign will pick up 1 record per agent.
How will this concurrent limit affect the dialer's ability to execute that pre-call rule data action for all 30 records? My understanding for the processing of a dialer contact list was that the dialer will grab all 30 records, processed them concurrently, then started feeding them out to the Edge device, if all of them have passed the pre-call rules.
Could anyone shed some light on this processing and relationship between a pre-call rule and the data action limit?
Just following up on this. Would you be able to help with the dialer use case that I detail in the post above? I want to make sure I am solutioning properly with the limits in mind.