Frequently Asked Questions

In order to enable reviews for changes that will impact your production environment, you need to follow certain steps. This includes changes to a dynamic config or gate, which affect rules with the production environment or apply to all environments. It also includes changes to an experiment that has started.

The philosophy behind this approach is to strike a balance between allowing developers to move quickly in a local environment, while ensuring that any changes that will impact end users will require a review.

Here's how it works:

1. Reviews are only required for changes that will have an effect on the production environment. This means that if you're making changes to a dynamic config or gate, reviews will only be required if these changes affect rules with the production environment or apply to all environments.

2. For experiments, reviews are only required for changes to an experiment that has started. This is because these changes could potentially impact your end users.

If you're seeing behavior that doesn't align with these rules, it's possible that there's a technical issue that needs to be addressed. However, in most cases, following these guidelines should ensure that your changes are reviewed appropriately before they're implemented in a production environment.