TheRealKevinGlinski | 2020-04-08 16:43:42 UTC | #1
Might need to be a support case here. When using /api/v2/conversations, the startAcwTime on a participant was populated after the conversation was disconnected and before the wrapup was assigned. Now it looks like that property doesn't get set until after the wrapup is assigned and the call is removed from the user's queue at which point endAcwTime is also set as expected. Was that change intentional?
tim.smith | 2020-04-09 18:05:15 UTC | #2
That change in behavior was not intentional and is likely a side effect of fixing another issue. Please report this to Care for investigation. It's worth mentioning CS-1511 in the case as a related issue. That issue is not a bug report for the problem you're reporting, but it's related.
system | 2020-05-10 18:05:16 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 7513