Hi, I’m wondering why I’m getting this “Invalid ex...
# ask-questions
c
Hi, I’m wondering why I’m getting this “Invalid experiment” error? I’ve set up a 50/50 experiment and am trying to associate it
@fresh-football-47124 any ideas? Thank you!
s
Are there any additional logs in the dev tools?
c
@strong-mouse-55694 can you explain where to check please? Is it adding
?gb-debug=1
to the URL and checking the console?
s
Sorry, I wasn't clear. If you're in the browser on that page in GrowthBook, are you able to open the dev tools in Chrome and see if there are any messages? https://developer.chrome.com/docs/devtools/open
c
Thanks @strong-mouse-55694! Here are the errors I get in the console:
Copy code
host-network-events.js:1  GET <https://growthbook-backend.groover.co/holdout?project=&includeArchived=> 404 (Not Found)
window.fetch @ host-network-events.js:1
await in window.fetch
(anonymous) @ auth.tsx:323
(anonymous) @ auth.tsx:348
(anonymous) @ useApi.ts:30
(anonymous) @ index.mjs:616
(anonymous) @ index.mjs:248
(anonymous) @ index.mjs:392
H @ index.mjs:386

host-network-events.js:1  GET <https://growthbook-backend.groover.co/holdout?project=&includeArchived=> 404 (Not Found)
window.fetch @ host-network-events.js:1
await in window.fetch
(anonymous) @ auth.tsx:323
(anonymous) @ auth.tsx:348
(anonymous) @ useApi.ts:30
(anonymous) @ index.mjs:616
(anonymous) @ index.mjs:248
(anonymous) @ index.mjs:401
e.isPaused.e.onErrorRetry.retryCount @ index.mjs:332
setTimeout
U @ index.mjs:478
(anonymous) @ index.mjs:329
await in (anonymous)
(anonymous) @ index.mjs:392
H @ index.mjs:386

host-network-events.js:1  GET <https://growthbook-backend.groover.co/holdout?project=&includeArchived=> 404 (Not Found)
window.fetch @ host-network-events.js:1
await in window.fetch
(anonymous) @ auth.tsx:323
(anonymous) @ auth.tsx:348
(anonymous) @ useApi.ts:30
(anonymous) @ index.mjs:616
(anonymous) @ index.mjs:248
(anonymous) @ index.mjs:401
e.isPaused.e.onErrorRetry.retryCount @ index.mjs:332

host-network-events.js:1  POST <https://growthbook-backend.groover.co/feature/o-and-s-price-placement/2/rule> 400 (Bad Request)
window.fetch @ host-network-events.js:1
await in window.fetch
(anonymous) @ auth.tsx:323
(anonymous) @ auth.tsx:348
(anonymous) @ index.tsx:689
(anonymous) @ index.esm.mjs:1996
await in (anonymous)
submit @ PagedModal.tsx:282
await in submit
onSubmit @ Modal.tsx:425
eU @ react-dom.production.min.js:54
eH @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
re @ react-dom.production.min.js:55
rn @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
oN @ react-dom.production.min.js:274
eF @ react-dom.production.min.js:52
ro @ react-dom.production.min.js:109
nU @ react-dom.production.min.js:74
nD @ react-dom.production.min.js:73

host-network-events.js:1  GET <https://growthbook-backend.groover.co/holdout?project=&includeArchived=> 404 (Not Found)
s
Thanks for that. It definitely looks like it's hitting some 404s. Are you using holdouts by any chance?
c
hm no we’re not
would it help to provide you any info about the test name/account/etc?
s
Are you on a paid plan by any chance? The errors indicate that something that should exist doesn't... Are you getting errors at all elsewhere?
c
We’re on a paid plan, and I haven’t run into other errors (though we don’t use the platform that much)
s
Thanks for the reply. Just to let you know, since you're on a paid plan, you can reach out to official support at support@growthbook.io or use the in-app chat. They may be able to provide more tools than I have to help. In the first message, to confirm, you're trying to add an existing experiment to a feature, right? Are you able to share a screenshot of that experiment?
c
Thank you! Here’s what I’m seeing on the experiment page
s
This all looks good. What happens if you: 1. Try to add this experiment to a new flag that you create? 2. Add a different experiment to the flag in question?
c
It seems to be happening to all experiments, here’s the same error with a different feature and new experiment: https://jam.dev/c/82ef3499-2c34-425f-b845-94411c77d763
s
Are you able to try a different environment?
c
We ended up getting it to work by upgrading to version 4.2 on our side 🙏
🙌 1