Closed BPMJoannette closed 3 years ago
@EFF the eventIds IMO should be guaranteed to be: 1) unique 2) temporal 3) incremental
so that we could sort messages by their IDs
With multiple servers running at the same time, that's a bit of a trick to achieve, but since the same incoming message is only processed by one server, it's safe to increment a local indice
More details on the cause of the issue here https://github.com/botpress/botpress/pull/4142
Describe the bug Sometimes two consecutive messages have the same timestamp, and appear out of order
![image](https://user-images.githubusercontent.com/62943352/95254544-0b696700-07ee-11eb-8f19-bd3228d46901.png)
In this example, the greeting is supposed to come first, then the choice skill.
To Reproduce Conditions unknown. I attached an edited version of the embedded-webchat example which has the botId parameter built-in, and the proactive trigger necessary to have the bot start to interact with us. I could not reproduce using this setup.
Expected behavior Messages displayed in order
Screenshots If applicable, add screenshots to help explain your problem.
Environment:
Additional context Customer-raised issue.