I’ve been getting this message quite often lately. Is it a local problem on my side, or do anyone else experience the same issue?
3 Likes
I have the same problem, so not only you. This message started appearing more frequently a few months back, but has only gotten worse so far in August.
On a good day it happens approx. once every hour, but today it is almost impossible to work in certain periods because it happens so often.
Got the same message, so used to it that I almost don’t notice it any more 
Thanks for the feedback. I’m experiencing the same issue in every location I work from, so it would surprise me if I were the only one with this problem. I normally keep several tabs open with different views from Create, but I don’t believe that’s the cause.
I’ve also experienced other issues lately, such as receiving random 503 messages while executing server calls.
Yesterday, I noticed several times that changes made in Create were not published to my dev environment. Refreshing the page in dev did not resolve the problem, but refreshing Create did. So something is definitely not right.
A patch aimed at reducing the number of “AmpSession already has socket assigned” error messages was released yesterday and will also be included in the new release tonight.
Please let us know if this fix leads to fewer error messages or if the problem persists.
Hi Olav! Great to hear that you are working on this 
I am receiving several of these today instead of the ampsession - don’t know if they are related:
Thank you for the feedback! A bit hard to tell if it’s related yet, but we will continue to monitor these errors.
Hello! The fix that was originally included in release 121 appeared to make things worse and has been reverted. A new fix was patched to production over the weekend and should hopefully result in a more stable user experience in Create.