Changes lost through merges?

[florian1]

Hi everyone,

I’m posting this here and not as a bug ticket because I don’t have steps to reproduce exactly.

I have a team of 3 people working full-time on our Bubble app (on the Team plan). Recently, we’ve had several cases where developers work on a task, merge it as a group of 2 (we do merge reviews), the modifications are deployed, and everything works fine.

And then a few weeks later, we find ourselves with a bug, linked to the feature previously deployed, and we can’t find our changes anywhere. Like it was never done.

At first, I thought “maybe the developers are mistaken and they did not make that change”, but I trust my team and the problem has been happening more and more (and since we do reviews, we have two people who are sure that the development had been done). And since we don’t have any version control on Bubble, there is no way to know why our changes disappeared.

The most concrete example I have of this: we had a trigger that made a call to an external API (something that belongs to us, written in C#). That call generated errors on the C# side (because of a legacy reason, the call was not supposed to be made anymore). So in our trigger, we removed said call to the other API. And we stopped getting errors.

A few weeks later, we started getting errors from our C# API. We looked at the trigger, and the call to the API was back.

We’ve had that happen several times now. As the CTO of the company, I am starting to get worried. If things we work on can disappear and we have no trace of it, it becomes really dangerous for our company.

As I said, I do not have steps to reproduce this. I post this here to see if anyone has had something similar happening. Any of you guys with similar issues?

Thank you,

Florian.

[georgecollier]

I’d have thought this was user error but there was another post a few days ago where someone’s workflow had disappeared in live. Maybe you can find it.

[Efe]

Hey @florian1, we have the exact same thing. And lately we’ve been noticing this especially in option sets. As you say, it is difficult to show the proof. We start building something again and again, every time. I also think it doesn’t come with branches. Before the update we sometimes notice something surprisingly reverting to the old version. It’s nice to know we’re not alone. I hope we get rid from it one day.

[ed19]

I’ve had bubble invalidate an entire datatype when merging, which broke my app completely. They kept telling me the ID of the datatype I was talking about was a mismatch to the datatype it should’ve been, but the “id” they were citing was actually the original datatype’s name (wild isn’t it). They kind of just ignored me and gave up because they couldn’t fix it and swore by the accuracy of their data provisions.

It’s been this way since the dawn of time, I’ve seen all sorts go missing, but at this point have just accepted it as COGS and resign myself to recreating things on occasion. Hasn’t happened to me since the branches update mind (at least not that I know of!)

[chad]

I also feel like this has happened multiple times