Hi guys! @calm-tailor-66162 @fresh-football-47124 Maybe someone could help me 🥺 I have an urgent question regarding a namespace we created and shared across different product teams. We’re currently receiving alerts that the namespace is full, even though new traffic is still coming in. We’ve tried doing a hard stop for the tests we’re close to entering, but it doesn’t seem to work. Could you please advise on how to resolve this? As I understand it, this might be related to GrowthBook’s inability to create more “rooms” within the namespace.

hi Yanina - we changed the functionality there - but we have a fix for this that should launch shortly

@fresh-football-47124, thank you for your reply! We’re still experiencing an issue with FF rules, users are unable to access the app. We’ve already reworked the attribute waiting mechanism. Could you please advise on what else we can do to help resolve this?

there should be a checkbox that lets you double assign

any possibility you could send a screenshot or video of what you're experiencing

Dear Bryce, give me sec pls

and to confirm, you are using GB Cloud, correct (not self hosted)?

We’re using GrowthBook Cloud on the Pro plan. 1. Do you have any CDN request limits? It looks like this might not be related to the namespace issue (just an assumption). 2. One SDK connection is working fine, but another one isn’t working in the production environment.

What are the symptoms you're seeing for 2?

The app is loading for around 1 minute, sometimes longer, then it opens with default values which are set up for the cases when GB does not return the actual values for FFs

is the issue perhaps that the default is "0 to 0" (which effectively means no traffic)? If you manually set to another range (like 0 to 1) does it solve the problem?

if so, this is an easy fix on our end, but hopefully you are already unblocked by manually setting the range and checking the "allow overlap" box

Hi Bryce, no, not really. It says that we have no available allocation left. If I select "Allow Overlap", I can allocate the traffic, and then I can remove the checkbox and still be able to create an experiment. Here is what our tech team saying: on production connection: After initializing GrowthBook, when calling growthBook.getFeatures(), the refreshHandler callback returns the following error:

Error: Optional("The operation couldn't be completed. (GrowthBook.SDKError error 1.)")
Code: Optional(GrowthBook.SDKErrorCode.failedToFetchData)
Underlying: nil

on dev connection: there is no error All other code remains unchanged. except connection id ClientKey - is correct

sounds like an SDK level issue, which SDK are you using?

recent patch release

1.1.4

for the swift sdk addresses this issue.

Thank you, guys, for helping to resolve the issue

Your level of involvement and willingness to support is truly impressive! it made a real difference ❤️

yes, it's safe if you understand what that implies. It doesn't inherently introduce statistical risk

Hi! Is it safe to update the self-hosted version to the latest commit and assume that namespaces will work without updating the Swift SDK?

The previous version of the Swift SDK is not compatible with the new version of namespaces, which were introduced as an option in the latest GB version. That said, you can now pull the latest GB version and still continue to use the previous "legacy" version of namespaces; using the latest GB build will remain safe for Swift if you do this