Deallocate before processcalllog

Genesys Cloud Integrations Embeddable Framework
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:

  1. Inbound call
  2. Processcalllog on connect.
  3. Type in comments
  4. Disconnect call
  5. Processcalllog called with comments in #3
  6. Type new comments
  7. wait for call to deallocated
  8. Interaction Event with deallocate called
  9. Process Call log called

See video link.

This is breaking our logic as we do some cleanup on deallocate.

2

Any feedback? Should I be taking this to support?

3

There's no guarantee of order on those messages

4

Thanks for confirming that is the case.

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.