Hello,

We noticed an odd issue with an interaction. It seems like the interaction was stuck in wrapup time/ACW for 15 hours, and from what I know there's only a maximum of 900 seconds time limit for ACW. I looked into the interaction details using API explorer but didn't notice anything out of the ordinary (unless I missed something).

Only thing out of the ordinary was this wrapup's direction was "Inbound" as opposed to "Outbound", could this be the reason why?

This queue has Optional ACW with no timeout.

What do you have the ACW set to for that queue?  The 900 seconds refers to the max you can set for the timed box, not maximum time, especially if you have optional or discretionary set.  

Hello,

We noticed an odd issue with an interaction. It seems like the interaction was stuck in wrapup time/ACW for 15 hours, and from what I know there's only a maximum of 900 seconds time limit for ACW. I looked into the interaction details using API explorer but didn't notice anything out of the ordinary (unless I missed something).

Only thing out of the ordinary was this wrapup's direction was "Inbound" as opposed to "Outbound", could this be the reason why?

This queue has Optional ACW with no timeout.

Hello,

We noticed an odd issue with an interaction. It seems like the interaction was stuck in wrapup time/ACW for 15 hours, and from what I know there's only a maximum of 900 seconds time limit for ACW. I looked into the interaction details using API explorer but didn't notice anything out of the ordinary (unless I missed something).

Only thing out of the ordinary was this wrapup's direction was "Inbound" as opposed to "Outbound", could this be the reason why?

This queue has Optional ACW with no timeout.

Hi Dianne, 

I have a related query based on your question, I had a similar scenario where the interaction wasn't 'wrapped' up for 15 hours, the wrap-up was set to 'optional' so no timeout, however, i was looking at wrap-up performance view for that particular queue and the Average ACW didn't seem to include the data from the interaction that was in ACW for 15hours, i wonder whether you noticed the same?

Hello,

We noticed an odd issue with an interaction. It seems like the interaction was stuck in wrapup time/ACW for 15 hours, and from what I know there's only a maximum of 900 seconds time limit for ACW. I looked into the interaction details using API explorer but didn't notice anything out of the ordinary (unless I missed something).

Only thing out of the ordinary was this wrapup's direction was "Inbound" as opposed to "Outbound", could this be the reason why?

This queue has Optional ACW with no timeout.

I think i found the why the interactions wrap-up wasn't including in reporting and it's because Genesys flagged the interaction, i found this by adding some the error column in the 'Interactions' view.

Hi Dianne, 

I have a related query based on your question, I had a similar scenario where the interaction wasn't 'wrapped' up for 15 hours, the wrap-up was set to 'optional' so no timeout, however, i was looking at wrap-up performance view for that particular queue and the Average ACW didn't seem to include the data from the interaction that was in ACW for 15hours, i wonder whether you noticed the same?

Hello,

We noticed an odd issue with an interaction. It seems like the interaction was stuck in wrapup time/ACW for 15 hours, and from what I know there's only a maximum of 900 seconds time limit for ACW. I looked into the interaction details using API explorer but didn't notice anything out of the ordinary (unless I missed something).

Only thing out of the ordinary was this wrapup's direction was "Inbound" as opposed to "Outbound", could this be the reason why?

This queue has Optional ACW with no timeout.

hi! If you looked at this agent stats for the day when interaction was handled you may not see a spike in Avg ACW for the agent, because Genesys would capture ACW on the moment interaction was completed I guess. As it happens with most of the reporting where "activities" are captured on the interval they happen, not like in "good" old CXI ;)

Genesys folks, please, let me know if I am wrong here :)

I think i found the why the interactions wrap-up wasn't including in reporting and it's because Genesys flagged the interaction, i found this by adding some the error column in the 'Interactions' view.

Hi Dianne, 

I have a related query based on your question, I had a similar scenario where the interaction wasn't 'wrapped' up for 15 hours, the wrap-up was set to 'optional' so no timeout, however, i was looking at wrap-up performance view for that particular queue and the Average ACW didn't seem to include the data from the interaction that was in ACW for 15hours, i wonder whether you noticed the same?

Hello,

We noticed an odd issue with an interaction. It seems like the interaction was stuck in wrapup time/ACW for 15 hours, and from what I know there's only a maximum of 900 seconds time limit for ACW. I looked into the interaction details using API explorer but didn't notice anything out of the ordinary (unless I missed something).

Only thing out of the ordinary was this wrapup's direction was "Inbound" as opposed to "Outbound", could this be the reason why?

This queue has Optional ACW with no timeout.

I think i found the why the interactions wrap-up wasn't including in reporting and it's because Genesys flagged the interaction, i found this by adding some the error column in the 'Interactions' view.

Hi Dianne, 

I have a related query based on your question, I had a similar scenario where the interaction wasn't 'wrapped' up for 15 hours, the wrap-up was set to 'optional' so no timeout, however, i was looking at wrap-up performance view for that particular queue and the Average ACW didn't seem to include the data from the interaction that was in ACW for 15hours, i wonder whether you noticed the same?

Hello,

We noticed an odd issue with an interaction. It seems like the interaction was stuck in wrapup time/ACW for 15 hours, and from what I know there's only a maximum of 900 seconds time limit for ACW. I looked into the interaction details using API explorer but didn't notice anything out of the ordinary (unless I missed something).

Only thing out of the ordinary was this wrapup's direction was "Inbound" as opposed to "Outbound", could this be the reason why?

This queue has Optional ACW with no timeout.

Hello,

We noticed an odd issue with an interaction. It seems like the interaction was stuck in wrapup time/ACW for 15 hours, and from what I know there's only a maximum of 900 seconds time limit for ACW. I looked into the interaction details using API explorer but didn't notice anything out of the ordinary (unless I missed something).

Only thing out of the ordinary was this wrapup's direction was "Inbound" as opposed to "Outbound", could this be the reason why?

This queue has Optional ACW with no timeout.