@tylersantos Which browser are you using? we were getting that error in IE in the UI, i think it was a cache issue