Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

variation traffic allocation paused by default #53

Open
kutnickclose opened this issue Jun 25, 2015 · 2 comments
Open

variation traffic allocation paused by default #53

kutnickclose opened this issue Jun 25, 2015 · 2 comments
Milestone

Comments

@kutnickclose
Copy link

expected: variation traffic evenly allocated by default
actual: variation traffic paused by default.

I launched a test that I had used optcli to push up the variations. Didn't realize the traffic was paused for the variation I had pushed up to optimizely until after starting test.

@nselvidge
Copy link
Contributor

Optimizely has stated that this is a known issue with their API. Their is_paused field on the variatons does not seem to work. I just went through and tried pushing some variations with that set and nothing is happening for me. I was able to set the weight field successfully, but that doesn't update the weight of any currently existing fields and led to the total weight of all variations being over 100%.

For version 1.0 we're planning on adding a unified optcli push command that will allow us to overwrite the default variation that is created with the experiment, and we could then be smarter about setting the weight field when we push the variations, but beyond that I think this will have to wait until optimizely fixes it.

@nselvidge nselvidge added this to the 1.0.0 milestone Jul 1, 2015
@nselvidge
Copy link
Contributor

Tentatively adding this to the 1.0.0 roadmap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants