Setting up workflows/plugins - Bug?

[PedroB]

Finally!

[samir.ahres]

Ho no, the hollydays were very short

[developer.charleslo]

Just upgraded my account and found out this bug is happening from my side as well.

[Sarah_Esteve]

[edit] things are back for wf and plugins

Plugins are back but not wf nor actions nor apis

[deejay.shani]

Working fine for me now !!!

[kokosiouli]

Well done guys, all is working again
Thank you!!!

[jonah.deleseleuc]

Looks fixed now

[stefanof]

Plugin and wf actions are back here

[keith]

Yeah, so stuff is restored… But… what WAS that? Eh? This is the third (fourth?) plugin-related weirdness in the last few weeks. Great if Bubble is working on plugin APIs, but ? I’m on strike developing new plugin code until client-side actions have parity with anything resembling a reasonable API, but still.

[redvivi]

@keith

Yeah, so stuff is restored… But… what WAS that? Eh? This is the third (fourth?) plugin-related weirdness in the last few weeks.

As I suggested earlier

@redvivi

We all know here that there will always be bugs in softwares. What matters is how they are handled and what we learn from them.

Perhaps post-mortems reports would be welcome @josh @emmanuel . As I was saying, most of us are not “users” but businesses and project owners entrusting Bubble to propel them above and beyond.

[erika.fukuda.dn]

What was the cause of this bug?

[josh]

Posted an update here: Outage this morning

(As a new thread so people will see it…)

[redvivi]

@redvivi

Realistically, we all know what’s happening.

Bubble is aware and one or several devs are working their arses off to prepare an emergency release, we just don’t know it.

@josh

We had some engineers working on the problem, but due to some miscommunications / lack of process clarity, no one currently awake was handling outbound communication to they forum or our status page. The engineers working on it were mostly heads-down trying to solve the problem, which was the correct response given what they had been told to focus on.

Yup, and I concur, that was the right thing to focus on @josh

[orth.dev.38]

Or just a day?))