i refreshed the page and that seems to have fixed the problem. it was just really interesting timing considering what happened right before the error
