nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Connectivity mail logs "Circuit breaker is open..."

Jim Ruby

These appear to be a transient error that doesn't cause a problem but I was wondering if there is a reasonable way to stop them?

"CircuitBreaker 'jepp.outboundauth.token.connection' is OPEN and does not permit further calls"

"Unexpected response received from jepp.outboundauth.token.connection response with status 502"

Thanks.

Accepted answers

All comments

Jack Brickey

Hi @Jim Ruby , these appear foreign to me in native JSM. I wonder if this is related to some addon app? Where are you seeing these messages?

Kevin van t IJssel

All of a sudden I experience the same. Since atleast august 12th and nothing has changed on the Microsoft 365 end though. Seems like a bug on Atlassian Cloud side. Because of this, e-mails aren't being imported anymore.

Schermafbeelding 2024-08-19 093237.png

Jack Brickey

I would send a request to Atlassian support to have them check it out.

Jim Ruby

@Jack Brickey We have a team project in JSM that's showing the errors in the e-mail channel connectivity log. They happen at somewhat random times and don't seem to be affecting the incoming messages. It's just some clutter that makes me wonder if there is some underlying issue we need to address.

Jack Brickey

@Kevin van t IJssel , if you do open a request with Atlassian, please update is here with the outcome.

Sonya McNeely

@Jim Ruby ,

We also had these; they started on August 6th and stopped on August 16th; with no change on our part. I cannot be sure if ours were pausing or stopping the fetching of the emails. Did yours prevent the fetching of emails? Did your errors stop?

Jim Ruby

I had kind of stopped looking at the logs because this wasn't causing any problems (that we were aware of), but I just checked and they stopped on Aug 16 just like yours. And similarly, we didn't make any changes around that time either.

Sonya McNeely

Yeah, I can't confirm any actual problems for us (besides the logging), and since it ceased the same time yours did I'm chalking it up as an Atlassian blip and moving on. Thanks for the reply.

Bernd Gurn

We are facing this with an Microsoft account since January 2026. It started on 25.01.2026.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management