Firestore connection bug

Can you add the flag for https://glede.retool.com/ as well?

@Tess @BAbarquez https://shiftapp.retool.com/ as well please. Thanks!

@Tess @BAbarquez can you add https://midasgames.retool.com/ as well please, thank you!

@Tess @BAbarquez can you also add this to bingenetworksadmin.retool.com.
Thanks!

Please can you add this for us as well getscope.retool.com

Hey @Tess @BAbarquez , Can you please add bingenetworksadmin.retool.com.
To this also as we finishing the developement on the app and this is going to make this into a long haul.
Please let me know if you need any input from us for the permanent fix.
Thanks!

same here, our operations team is down, can you help us fix it asap?
https://webot.retool.com/

Why are you not rolling back the release instead of letting dozens of people ask you to add a feature flag for them? This is clearly a regression that came form not testing your release.

You received the first report 4 days ago and still have no solution or information for your users.

In any case please enable the flag for https://craftnote.retool.com/ so we can use your product again

3 Likes

Can you add it to sdenv.retool.com as well?

Hello, could you add oneflash.retool.com as well ? Thank you

@Tess @BAbarquez There is any real solution for this problem? Please, add feature flag to https://somei.retool.com/ . But i realy recomend you to take an action that can fix the problem globally, not only for the ones who send you the domain here.

Agreed! Just some honest feedback. Giving up full control over source code to make building UIs faster through a tool like Retool requires a lot of trust and high expectations of Retool. Having to jump through hoops to fix an avoidable bug like this and the time it takes to correct is very concerning. Retool's performance is reflected in the developers that use their product and have to answer for issues like this. This loses a lot of momentum and trust in investing time into building out tools with Retool. I've loved the product, but I'm trying to be honest about its shortcomings. We are moving our Retool apps to a custom-built app because the risk of issues like this outweighs the speed of building quick prototypes.

1 Like

Hey there! Just enabled the feature flag for everyone else in the thread.

I also definitely understand your frustration with the way this was handled.

For full transparency, this regression did not land on our radar until yesterday as we had no proactive monitoring in place for this error. Within the first hour that it was discovered we were able to identify a low-lift workaround (enabling the feature flag and setting the database name to (default)) for affected organizations. This allowed our engineering team to focus on a fix forward as opposed to rolling back the change to our code.

The permanent fix will go out later today and we will update you here on when it lands in production!

1 Like

I think maybe you could run something like a migration that enable this feature flag for all users with the correct (default) configuration already. That would be a realy better sollution. And then, when you manage to fix permanentely, you could remove it. Just a sugestion. Cause, the ones who dont find this thread will keep with the problem.

1 Like

Help me urgently. We are stuck with a client here looking to our face with "friends no more" expression https://divy.retool.com/

Also after enabling the feature flag you will have to set the Firebase database name to (default):

Just enabled @Octavio_Turra!

1 Like

Hi, could you enable the feature flag for my organization too?

bellify.retool.com

Done @Gianluca_Chiesa_Pastor!

1 Like

Same issue here. What's a good email to reach you @BAbarquez