Hi Freddy,

This is probably the effect of Optimistic locking.

If you started an Edit on a record, and another person edits that row too, then your record would not contain the latest data and could save the wrong data. You are notified when this happens.

Then it's super buggy, because I get it switching tabs and just read operations. Besides that there is no column in the model that uses optimistic locking. 

It could also have to do with a 409 status code, but I lack the experience with this. Perhaps ​@Alexandra Egri can help out.

​@Mark Jongeling ​@Alexandra Egri it has nothing to do with a 409 status code, but with a 500 status code that states the connection has been terminated..  I just found out that that the latest CU17 update of SQL server is not functioning very will on linux/container. I went back to CU16 and so far so good. 

I ge the mention message in combination with a 500 Internal Server error and in the error log the reason is: 

-->A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 2 - Connection was terminated)

Hi ​@Freddy,

Given your current findings about the CU17 update, do you still require assistance regarding this topic?

No, besides that the message given is not correct.