There is an issue with the current build and Insert Record server behaviors. You must have re-applied that server behavior to re-introduce the problem. I've fixed it on your page. I'm hoping to get a new build out early next week to address this problem.