Confluence failed to load space

[bounaux]

Hello, 

We're testing confluence product and it's showing this message: 

We’re having trouble loading the spaces. Try refreshing the page.

Atlassian and bitbucket loads OK.  Attempted to clear browsing data or login cognito mode don't help.

Chrome shows dump:

cc-fe-bifrost.prod-east.frontend.public.atl-paas.net/assets/master/force-update.json:1 Failed to load resource: the server responded with a status of 404 ()Understand this errorAI bundle.esm.js:63 Uncaught (in promise) Error: GraphQL error: Exception querying the remote GraphQL service: io.atlassian.platform.micros.asynchttp.UnexpectedHttpStatusResponseException: Unexpected status code 429 at new t (bundle.esm.js:63:28) at bundle.esm.js:1247:40 at bundle.esm.js:1569:25 at Set.forEach () at bundle.esm.js:1567:32 at Map.forEach () at e.broadcastQueries (bundle.esm.js:1555:22) at bundle.esm.js:1659:27 at Object.next (Observable.js:322:23) at b (Observable.js:135:18)Understand this errorAI rest/create-dialog/1.0/spaces?promotedSpacesLimit=1&otherSpacesLimit=1&promotedSpaceKey=:1 Failed to load resource: the server responded with a status of 500 ()Understand this errorAI cc-fe-bifrost.prod-east.frontend.public.atl-paas.net/assets/master/force-update.json:1 Failed to load resource: the server responded with a status of 404 ()Understand this errorAI cc-fe-bifrost.prod-east.frontend.public.atl-paas.net/assets/master/force-update.json:1 Failed to load resource: the server responded with a status of 404 ()Understand this errorAI 2react-dom.profiling.min.js:205 Error: GraphQL error: Exception querying the remote GraphQL service: io.atlassian.platform.micros.asynchttp.UnexpectedHttpStatusResponseException: Unexpected status code 429 GraphQL error: Exception querying the remote GraphQL service: io.atlassian.platform.micros.asynchttp.UnexpectedHttpStatusResponseException: Unexpected status code 429 GraphQL error: Exception querying the remote GraphQL service: io.atlassian.platform.micros.asynchttp.UnexpectedHttpStatusResponseException: Unexpected status code 429 at new t (bundle.esm.js:63:28) at t.getCurrentResult (bundle.esm.js:159:28) at t.getQueryResult (react-hooks.esm.js:265:62) at o.getExecuteResult (react-hooks.esm.js:73:32) at t.execute (react-hooks.esm.js:106:51) at v (react-hooks.esm.js:380:95) at f (react-hooks.esm.js:354:42) at h (react-hooks.esm.js:397:12) at i (use-query.ts:12:23) at ProductHome.tsx:54:35

Any suggestion pls? 

[Dave Liao]

Hopefully this is a temporary interruption? Is this still happening?

You can check Confluence Cloud’s overall status here: https://confluence.status.atlassian.com (I’m seeing green across the board, so hopefully you’re OK)

[bounaux]

Just checked still the same problem, any idea on how to restore service? Thx!

[Dave Liao]

Not sure!

• Are all your users seeing this?
• Have you tried accessing your Confluence instance from a different machine?

[bounaux]

Yeah just checked on my ipad, same problem.

[Dave Liao]

@bounaux 

I just escalated this request to Atlassian’s support team (I don’t work for Atlassian, I’m a volunteer!), especially since your team can access other Atlassian Cloud products, but not your own tenant.

[Jessica]

Hi @bounaux 

Currently there are no active incidents that could be impacting spaces or pages to be loaded. We haven't heard any similar reports as well, so we would like to investigate further what could be happening there and see if we can replicate the issue as well.

For that, we have created this support ticket on your behalf: https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-1079650

Please feel free to add any additional questions or information on this issue there and we should get in touch with you there soon! You can also grant us data access in the meantime by accessing the ticket and clicking on "Approve data access".

Regards,
Jessica

[Tomislav Tobijas _Koios_]

Hi @bounaux ,

In case this still appears to be an issue, I think you should be able to start a paid plan trial so you can submit a ticket to Atlassian Support. They could probably give you better assistance on the matter as they can (if granted) get access to your instance to inspect the problem further.

Hope you'll get this resolved.

Cheers,
Tom

[bounaux]

Ok thanks!