Concurrent sessions from the same browser

Hello,

I'm using lex-web-ui and have a working website with it running in an iframe. While testing I noticed that if I were to open my website in multiple tabs in the same browser and try to send messages all at once in each tab's instance, the messages I sent are handled sequentially by my backend lex bot lambda. This is not the case if I were to open the website in 2 different browsers.

I'm suspecting this is may be due to how AWS Cognito authentication puts the userID within local storage or something within the lex-web-ui logic itself that's detecting and preventing the concurrent executions from the same user (sessionID) within the same browser but I'm not sure. Could some one provide some insight and potential ways I can get around it if it exists?

My issue is similar to what was asked here: https://github.com/aws-samples/aws-lex-web-ui/issues/89

Start by reproducing simultaneous messages from multiple tabs running the lex-web-ui iframe, then inspect AWS Cognito authentication, browser local storage, and the lex-web-ui session handling mentioned in the report. Compare the behavior with separate browsers and with the related issue #89; done means identifying whether shared browser state causes serialization and documenting a confirmed workaround or fix scope.

Written by the indexing model from the issue text.