Creating scripted field briefly shows incorrect error message

[LeeDr]

Found on 4.4.0-snapshot with Elasticsearch 2.2 with Shield plugins.
Following test steps for Scripted Fields in https://github.com/elastic/kibana-qa/blob/master/settings.md when you finish creating the scripted field an error message shows up very briefly (too fast to read in my case). I saw it using IE and Chrome so I don't think it has anything to do with the browser.

The message is from kibana/src/ui/public/field_editor/field_editor.html;
Mapping Conflict:
You already have a field with the name {{ editor.field.name }}. Naming your scripted
field with the same name means you won't be able to query both fields at the same time.

But this message is incorrect. It doesn't seem to matter what name you give the scripted field.

The screen quickly switches back to the list of scripted fields and does show the one you just created. There's no way to go "back" to see the error message.
The new scripted field does work. So this message is misleading but harmless.

Not sure if it's in the previous 4.3.1 release, or master.

[rashidkpc]

This happens because you briefly do have a conflict. It shows up right after you save, but before you get redirected away from the page. So for a moment the index pattern has the field "bytes inverse", because you just created it, and the input is also called "bytes inverse". The form needs to know not to show that message during saving.

[LeeDr]

I just hit this on IE with Kibana 5.0 alpha1 and the message didn't go away.

It seems that the message staying, and scripted field NOT being created, were both do to a session timeout. I was stuck on the scripted fields page until I refreshed by browser, and re-logged in.