I'm getting the same error, I have been doing this for 5 years and never seen this error.
I have a feeling it is some sort of bug with the new back end.
Hopefully will be fixed soon, if anyone knows anymore please comment.
This is a very annoying bug.