Hello Please add us too https://uniodate.retool.com/
@Patrick_Alvarez @Stephane_BALASSE1 just turned it on for your organizations!
Please add to ours as well Bento.retool.com
@BAbarquez please do the same for skip.retool.com
@BAbarquez can you add me too ryestorebuilder.retool.com
@nery @Lucas_Tenorio @Ajibade_Adebayo done for all your organizations!
@BAbarquez https://servalventures.retool.com/ as well please. Thanks!
I have no idea where to find this setting that your already share with our domain, pls let me know asap where do I locate this config?
Added for your org, @ninjasitm and I sent you a DM, @Patrick_Alvarez
@Tess we are also facing the same issue.
ReferenceError: DEFAULT_FIREBASE_DATABASE_ID is not defined
Can you tell us what we need to do after you enable the temp fix for now ? can you do it for amiraise.tlcforkids.org.au
and this being down at the moment is very concerning for us as it stops all our operations...
Hi @Amir1,
Thanks for chiming in. I have added the flag for your org. Please see the instructions here: Firestore connection bug - #24 by BAbarquez
thnx that fixed it.
Can you also enable the flag for this org?
Hi, could you also add the feature flag for this organisation? https://yanokai.retool.com?
Thank you
Hi @Tess @BAbarquez
Will you be able to help with https://kustodian.retool.com/. ?
Our operations are halted due to this.
@Tess @BAbarquez ,
Can you enable to flag for https://plumhq.retool.com. Our ops team is heavily reliant on retool and they are completely blocked.
I am having the same problem on all my queries. It started last night, then after a while it worked for a while and now it is showing the same problem again today. This is one query example, but every query that used to work now shows the same error -
@Tess @BAbarquez,
The entire day of our operations team is being wasted. Please provide a fix for this or enable the flag for the workaround.
can you add the flag for https://angsana.retool.com/
This is our subdomain, and while it would be great if you could enable the flag quickly, I honestly don't understand this kind of response. Because of a mistake in your server code, this issue is now affecting all Retool Firebase users globally. Naturally, the response should also be global. The idea that only the subdomains that commented on this thread can get the issue resolved is, frankly, a ridiculous approach.
Also, a similar incident happened a few months ago. The fact that our service—built with reliance on Retool—can become unusable due to internal updates on your end is something you need to take very seriously if you’re aiming to make Retool a globally recognized, major platform. A platform should never be operated this way.

