• Why should I avoid individually targeting too many users?

    Individually targeting users increases the size of the payload fetched by the SDK when initializing, and the memory footprint of the SDK.

    A better strategy would be to assign a custom attribute to the users who should receive the feature flag and then set up the targeting rules to serve the flag to users who have that attribute. This allows you to target groups of users without increasing the size of the payload.

    You can read more about our targeting rules here. 

  • How long does it take for users to appear in the dashboard?

    It generally takes just a couple of minutes for a user to appear in the dashboard. 

    You can check the dev console to verify that the users data is being sent to LaunchDarkly. If you open the dev console in an active tab and call variations on your users, you will see them appear in the console almost immediately. This is a great option to make sure that LaunchDarkly is receiving your user data without waiting for users to appear in the dashboard.

  • How can I be notified of interruptions to the LaunchDarkly service?

    The best way to get updates from us regarding service status is by subscribing to this RSS feed: http://status.launchdarkly.com/

  • I am unable to connect because of a mismatched origin header
    We take the security of your data at LaunchDarkly seriously. One of the protections we've implemented is validation that the Origin header for any API request authenticated by session cookie matches the expected Origin header (namely https://app.launchdarkly.com). This is just one way that we help to prevent CSRF attacks. (Note that we do not require origin matching when authenticating via Access Token, so this does not affect normal API usage.)
     
    If the Origin header does not match what's expected, we return an error. And since our application relies heavily on interaction with the API, the application will not function properly.
     
    Known causes
    Any browser extension that intentionally changes the Origin header will cause this problem. For example, the Allow-Control-Allow-Origin: * Chrome extension is known to change the Origin header to http://evil.com and will result in the problems described above.
  • What does "Your configuration is incomplete" mean?

    If you're seeing the "Your configuration is incomplete" message, it will usually indicate that there is an incomplete or invalid rule configured for your flag. For example, this could mean that an attribute was not selected, or a negative number was selected for a percentage rollout.

  • Why are all my users seeing the same variant of my flag?

    Make sure that you’re sending distinct user keys for each user in your variation calls. A few other possibilities:

    • Your default rollout rule is serving a single variation
    • Your users are receiving the fallback variation because something is not working correctly
    • The kill switch was activated, and the feature is set to ‘Off’
  • How do you sync between environments? Can it be automated?

    We don’t have a “promote from environment A to B” workflow built into the tool yet, though we hope to be able to support this functionality in the future.

    An available workaround is to use our REST API to automate this. A common use case is to copy a flag's configuration from one environment to another:

    To do this, you will first use the Get feature flag endpoint to get the data from the flag you want to import: https://apidocs.launchdarkly.com/docs/get-feature-flag 
    Then, use the Update feature fag endpoint to update the flag configurations in production: https://apidocs.launchdarkly.com/docs/update-feature-flag

    We do have a script available that you can use to automate the process of syncing an entire environment: https://github.com/launchdarkly/sync-ld-flags

    It's important to note that this script does not work to copy in segments or any rules targeting users by segment.

  • The click goal editor cannot load my page

    The editor is failing to load your site through an <iframe> because of security restrictions. To ensure our editor works, add X-Frame-Options: ALLOW-FROM https://app.launchdarkly.com and Content-Security-Policy: frame-ancestors 'self' https://app.launchdarkly.com to the response headers of your site; alternatively remove the headers if you don’t need to restrict embedding of your site using an <iframe>.

    Note that Chrome and Safari do not respect the ALLOW-FROM directive. Also, Internet Explorer does not currently support Content-Security-Policy with frame-ancestors.

     
  • I am having trouble logging in to my LaunchDarkly account

    Password Help

    • If you have forgotten your password, simply click the “Forgot Your Password?” link on the login page.

    Multi-Factor Authentication (MFA)

    • If you are prompted to enter your MFA verification passcode, use the authenticator app on your mobile device to enter the six-digit code.
    • If you have forgotten your recovery code or you cannot access your phone, ask the administrator of your LaunchDarkly account to send you a recovery email.
    • Documentation