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; } } }

Somethings Gone Wrong error

Yatish Madhav

Hi there

Thanks for posting this, Louis.

I am experiencing the same this morning - I had a look at the https://status.atlassian.com/ page and all are Operational. But on few refreshes and some collegues doing the same doesn't resolve this.

It is displaying the error in the summary above either in the center of a blank page:

Screenshot from 2020-08-18 09-57-07.png

or on the bottom left:

Screenshot from 2020-08-18 09-57-23.png

Please advise where the issue is and how to better monitor this for our org?

Thank you

Yatish

Accepted answers

Ste Wright

Hi @Yatish Madhav

Atlassian is aware - I've been told an internal incident report has been raised.

Our instance also went down but it seems like its back now - so keep trying!

Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/

Ste

All comments

Ste Wright

Hi @Yatish Madhav

Atlassian is aware - I've been told an internal incident report has been raised.

Our instance also went down but it seems like its back now - so keep trying!

Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/

Ste

Yatish Madhav

Hi Stephen - thanks for the quick reply! Yeah, I have been refreshing that page and am monitoring ... All of them state operational so not entirely helpful I also need to send a notice to the users in our organization of updates and reasons too. Please keep me posted here of what the issue is and also once it is resolved? Thank you again

Ste Wright

Hi @Yatish Madhav

Just to add - the Status Page has now been updated with recorded incidents. This should help with sending a notification to your users

Ste

Yatish Madhav

Great - I just noticed that too just before I saw this notice come in. I have informed them.

I will keep monitoring it ... I wonder what it is

Thanks, Stephen

Yatish Madhav

Hey @Ste Wright - well done to the team on resolving the issue. Though some of our API calls (for example loading our Projects on our internal Connect App) still results in 503 Gateway Timeouts ... Is this related? also what was the issue? Thanks

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-desk