You can try 1200. We originally had that issue when it was 200 but I haven't heard it happen since we moved to 800. I'd have to see the error to really be confident, but it sounds exactly like the issue we had and increasing that number fixed.
Is it a particular browser or scenario that I might be able to follow to reproduce it?