[Experience Page] Experience shows as "This experience is currently not available"

Interesting. Marked as fixed but I see this is still happening.
image
I don’t really want to open up a new report as this doesn’t exactly keep all things related to the bug in one place. @thirdtakeonit is there a way you can revisit this issue? The scale may or may not be widespread but I am very concerned until I have a more definitive answer.

2 Likes

Adding additional user reports:



Until today, I thought this might have been only my account, but I have noticed in my discord community that other users have reported this issue as well.

1 Like

Sorry for the delay, it looks like this was marked as Fixed by accident which let it fall between the cracks. I asked our triaging team to take a look at this at priority during their next business hours.

2 Likes

(Not the triaging team)

We’re unable to reproduce this locally - Followed up in DM for more info :saluting_face:

Following up from DM with @Brick_man -

Recap:
This specific issue happens sometimes for certain users, only when this experience’s page is opened for the first time in the browser session.

(If you’re seeing this same error with a different method of reproduction, it’s not the same issue)

Issue Update:

We made a fix last week that should prevent this from happening in the vast majority of cases, and we haven’t seen it occurring since then. :crossed_fingers:

1 Like

It’s happening to me as of now. Tried refreshing and re-opening my browser too, nothing worked. (Using Opera GX)

1 Like

This has also happened to me yesterday

1 Like

Hi @Exaltrd , @Siyenide_Queen

The issue being reported in this thread is that:

  • the first time that the browser is opened, the experience shows as unavailable
  • refreshing the page fixes the issue

If you are seeing this exact behaviour, please send your user id and the link to the experience here.

If either of the above is not true (i.e. if this happens to you in the middle of the browsing session, or the issue persists after refreshing), please open a new bug report.