Genesys Cloud - Main

Hello All,

We are prioritizing interactions using the SetPriority feature  in Inqueue flow. It is working as expected.
But we wanted to see call jump after priority setting, so we used call.positioninqueue inbuilt variable to check the position before and after priority setting.
we printed the position in participant data.
But after checking we came to know that position before and after priority setting is same.
we tried printing the number of  waiting calls in queue before routing the call to queue, so we can get to know the initial position of call before coming to queue, but no use there also.
Can anyone help me understand this scenario, why call position in queue is not changing after setting priority also.

Hi Gowtham - this is unfortunately a limitation in analytics where they are not able to process the update event.  We are looking for ways to address this but I don't have any timing on it currently.  The conversation itself will have the correct priority value but there isn't an easy way to 'check it.'

Hello All,

We are prioritizing interactions using the SetPriority feature  in Inqueue flow. It is working as expected.
But we wanted to see call jump after priority setting, so we used call.positioninqueue inbuilt variable to check the position before and after priority setting.
we printed the position in participant data.
But after checking we came to know that position before and after priority setting is same.
we tried printing the number of  waiting calls in queue before routing the call to queue, so we can get to know the initial position of call before coming to queue, but no use there also.
Can anyone help me understand this scenario, why call position in queue is not changing after setting priority also.