"Sorry, we ran into a temporary bug"

1theritzy · 2025-01-30T17:21:03.811Z

A user got this message today on my site. I’ve never seen this before, is it common? What is the cause?

georgecollier · 2025-01-30T17:44:45.927Z

It’s not common, but is generally something only Bubble can fix. If it’s not regular, don’t worry about it, and if it is, open the browser’s develoepr console, and send the error message to Bubble in a bug report.

1theritzy · 2025-01-30T17:51:36.229Z

Thanks George. I haven’t seen this in 2 years operating.

georgecollier · 2025-01-30T18:08:09.075Z

Lucky you!

1theritzy · 2025-01-30T19:50:03.750Z

But I have seen a veritable plethora of other page errors, mostly “page unavailable” that I still have not been able to resolve.

85bears · 2025-01-30T20:57:40.899Z

I got this error today. I deleted the workflow it was triggering and redid it with the same steps and it solved the issue FWIW.

1theritzy · 2025-01-30T21:52:46.128Z

You mean you deleted the specific workflow action and replaced it with an identical action? How do you know that fixed it, or it just went away temporarily? I did nothing to mine and that fixed it too.

85bears · 2025-01-31T14:07:44.643Z

that’s fair. The answer to your questions are yes and I have no idea other than it was 69 seconds between error and fix. Your approach certainly sounds solid. It hadn’t worked for me in the past for sometimes hours, so I thought I’d just…you know…try something.

1theritzy · 2025-01-31T15:13:47.796Z

got it, interesting, thanks! Keep up the great work Bear.

85bears · 2025-01-31T15:59:34.116Z

lol it’s happening again and my “fix” didn’t work this time… Boy am I getting tired of this one.

1theritzy · 2025-02-01T17:05:33.253Z

AHA! You might try my solution.

85bears · 2025-02-01T17:48:50.714Z

I’ve executed your protocol

1theritzy · 2025-02-01T17:54:48.209Z

Working yet?