if user returns, they will have same cookie (if not expired) -- message count will start over at zero overwriting current dynamodb entries
this behavior was caused by the application server restarting. application memory is lost. client comes back in with same cookie id, causing an overwrite at mesasge 0. solution was to also generate a uuid in memory for the chat.
if user returns, they will have same cookie (if not expired) -- message count will start over at zero overwriting current dynamodb entries
this behavior was caused by the application server restarting. application memory is lost. client comes back in with same cookie id, causing an overwrite at mesasge 0. solution was to also generate a uuid in memory for the chat.