Sorry for the delay, so this seems to have been caused by our earlier latency issues. Other users reported the same issue as well, you can try re-running the table and it should work now. Also one of my coworkers managed to get another table to run for you as well.