Oops! Something went wrong. Please reload the page and try again. X

kevincunno

Hi jaymailsays I should have kept my mouth shut the other day I have had the same problem you mentioned a few times today sadly 😞

jaymailsays

kevincunno have had the same problem you mentioned a few times today sadly

In which case it wasn’t addressed in the overnight platform update 🤒

harrrrrry

Right at the moment, I’m getting that error reproducibly on a specific thread, which is interesting because usually it’s an intermittent problem that goes away long before we get a chance to try to work out why it’s happening.

The thread is https://community.giffgaff.com/d/22259036-more-efficient-way-to-keep-helpers-in-the-loop and at the moment the index points to https://community.giffgaff.com/d/22259036-more-efficient-way-to-keep-helpers-in-the-loop/38.

Currently, all posts up to /19 can be retrieved by appending the message number to the command line
Additional posts up to 28 can be retrieved by scrolling down but attempting to scroll down to post 29 generates the Red X error
posts between 20 and 28 can’t be retrieved from the command line. But instead of the Red X I get a plain text message “An error occurred while trying to load this page”.

Possibilities:

the thread might be corrupted
control-F5 does not change anything, so it’s probably not due to cached content
but it’s a thread that’s regularly updated by staff – and was posted on a few days ago, so if the thread is corrupted it has happened very recently
in the index for Contribute, I see this against the thread:

So … it seems likely that the corruption (if that’s what it is) or whatever caused the problem happened 20 minutes ago.

Could it be that @pal2j57 is still actively editing the message, and that’s what’s causing the error?

@alex_w Any way of checking whether something different happens when staff create messages?

z201205

harrrrrry happens for me too.

alex_w

harrrrrry

This thread now appears to load correctly - suspect it was suffering from the same bug that we’ve now tracked down as being the cause of the other issues we had last night.

harrrrrry

Oh, I’ve noticed something extra.

I assumed pal2j57 was a new member of staff. But here’s what the message says, according to the member’s profile:

So … that was actually an off-topic message and probably it has been flagged to an educator and either is being or has been moved to a more appropriate place.

The member’s post list is still showing a broken pointer to the end of the “More Efficient Way…” thread so it’s broken there too. So, either the move is still in progress or did not successfully complete.

But it possibly helps get us closer to finding one of the causes of the Red X error.

jaymailsays

harrrrrry
It is a strange one, refreshing the page makes no difference.

harrrrrry

jaymailsays

… and still broken now, for that particular thread.

jaymailsays

harrrrrry
I reported it earlier.

Dez is on the case

kimchi

jaymailsays I’m getting that message when trying to access general discussion…

jaymailsays

kimchi
Try refreshing your browser to encourage giffgaff.com to recognise your device. It can mean you have temporarily timed out.

killian12

alex_w
Same thing happened to me last night too. Was fine this morning and no problem since. 😊

cestephanou

I think it happens when the internet drops out a little bit but still connected. Very annoying. I usually just wait and it starts working again quickly.