Mike McLaughlin

https://github.com/sourcegraph/accounts/issues/6716 is very interested in this. see this [internal slack thread](https://sourcegraph.slack.com/archives/C01D50MSA7L/p1659431596108699).

From @stefanhengl : > The newer version showed the error. However, we didn't confirm yet on our side that 5.16.3 doesn't show this error.

@ryanslade they said they likely have some rate limiting enabled but they are not sure and the team that runs these servers is not very responsive so we likely won't...

ok. it seems to happen regularly. anything else I can gather from the logs to help us?

Customer has not seen this error since removing the one problematic Bitbucket server from Sourcegraph. When we re-added that server back to Sourcegraph, we did not see the exception. However,...

@indradhanush it happened one more time on a new server: > This error is generated for the new cluster we were trying to add. Once we get this error it...

Confirmation that this is still happening (per meeting with @indradhanush and @stefanhengl ): > I added new projects to the existing config. > Just to confirm the new projects that...

updating the priority from p1 to p2 since the workaround of waiting for it to fix itself is sufficient for the short term. we should definitely fix this, but we...

Great write up @varungandhi-src! Adding a link to the [customer](https://github.com/sourcegraph/accounts/issues/8004) [discussion](https://sourcegraph.slack.com/archives/C05EA9KQUTA/p1704833360209399) that prompted this so it's easier to find when they ask about it.

Requested by https://github.com/sourcegraph/accounts/issues/6938