We're currently implementing a new task routing workflow for a customer. During SocialMiner API and Finesse Client testing everything went well regarding rona. But in the ucce call flow we can't check if rona occured.
Most customers require to increase priority if the call is requeued, but Call.RequeryStatus is always 0 and indicates that no rona occured.
It's the same issue if dialogLogoutAction is set to transfer. The task will be requeued to the original script selector without notice that there was some kind of failure.
Workarounds:
- For non real time applications (like document/e-mail routing), we'll set start timeout to a high value to limit the rona cases. However, there's still the issue with dialogLogoutAction...
- For real time applications like chat and for the dialogLogoutAction issue, we'll query Call.RouterCallKeySequenceNumber. If it's greater than 0, the task visited a call flow already, indicating that rona or dialogLogoutAction occured.
- This won't work if agents are required do transfers to script selectors, but we don't need that feature at the moment.
- If requeue on recovery occurs (e.g. pg cycle/failure), tasks are requeued with fresh RouterCallKeys and will start over with RouterCallKeySequenceNumber = 0.
