This is a known issue. Since this is due only to GitHub rate limiting, the current work-around is to try again later.