We’ve partially resolved this issue. RobotEvents apparently changed the date format they used in the API which caused the date parsing on our side to fail, and we’ve now adjusted to their new format.
However, we normally only populate out the next few weeks’ worth of events in VEX via, and the invalid dates caused events further out than that to be published. The fixed code has now gone back to ignoring those events since they’re further out, but that means those events are still showing in via with the invalid date. We need to figure out some other way to deal with that side effect.