Michael.Shrall | 2019-10-18 02:28:36 UTC | #1
We are experiencing a situation where the interaction event "deallocate" is called before "processcalllog" in a specific scenario. Given deallocate is usually the last event for any interaction, shouldn't the processcalllog come before the deallocate?
Scenario:
- Inbound call
- Processcalllog on connect.
- Type in comments
- Disconnect call
- Processcalllog called with comments in #3
- Type new comments
- wait for call to deallocated
- Interaction Event with deallocate called
- Process Call log called
See video link.
This is breaking our logic as we do some cleanup on deallocate.
Michael.Shrall | 2019-10-31 17:15:05 UTC | #2
Any feedback? Should I be taking this to support?
Richard.Schott | 2019-10-31 18:00:12 UTC | #3
There's no guarantee of order on those messages
Michael.Shrall | 2019-10-31 19:16:54 UTC | #4
Thanks for confirming that is the case.
system | 2019-11-30 19:16:56 UTC | #5
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 6282