- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
What does your transfer to queue flow look like that is associated to the quick connect?
david
It's the default queue transfer flow that's preconfigured by Amazon. I modified it by putting a voice prompt (i.e. saying "Starting transfer flow") to play as the first step before continuing into the pre-defined behavior. This prompt never plays.
I've also tried it with a queue transfer flow that has two blocks: one explicitly sets the destination queue (although I'd expect this is already set within the quick connect) and then sends it straight to transfer. This also doesn't complete the transfer.
I had the same issue, as some point AWS reduced the concurrent calls service quota to 1 although the service quota portal said 10. Once I raised a ticket to increase this value the problem was solved.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 mesi fa
Have you turned on logging? Check the logs in cloudwatch, they will tell you exactly what is happening.
Hi, did you manage to resolve this?
I have just had it today on a new Connect instance. Exact same scenario - outside Quick Connects are fine, but queue ones are failing, with default queue transfer flow. If I turn logging on within the Flow, I don't see anything in CloudWatch logs. Also no errors on CCP console window etc.