That’s a problem on our side, not something you did. The most likely reason is that we’re part-way through rolling out a change — and it doesn’t affect the scans running on your repositories, which are handled somewhere else entirely.
Refreshing usually fixes it, and if we are mid-rollout it will fix itself shortly. If it keeps happening, tell us and we’ll look — you won’t be the only one seeing it.
Reload