Start Free trial

Articles in this section

Manage SDK Settings in Wingify Feature Management

Shweta Ajwani
  • Updated
Share:
close this to read article
Feature Availability: Access to this feature and some of its options depends on your plan. To check your current plan, see View my plan and subscription details. For details on what each plan includes, see Wingify Plans and Features.

This article covers the following:

Overview

Wingify provides advanced settings to manage your SDK instances effectively across different environments. These settings help you control how configurations update and provide a safety switch to disable SDK operations instantly during critical situations.

For example, if you update targeting conditions or rollout percentages in Wingify Feature Management, you can force the SDK to fetch these modifications immediately rather than waiting for the next automated sync cycle. Similarly, if a live feature causes a critical issue on your application, you can use the disable option as a kill switch to revert your application to its default state immediately.

Once the SDK is initialized, it periodically pulls the latest flag, rule, and variation configuration from Wingify on its own schedule via polling. The advanced settings give you two ways to intervene outside that schedule, per environment:

  • Force SDK refresh: Pulls the latest configuration immediately.
  • Disable SDK: Stops the SDK from serving Wingify configuration to your application altogether.

This article further covers both actions in detail.

Prerequisites

Access SDK Settings

To access the management options for your SDK:

  1. Log in to your Wingify account.
  2. Select Configurations from the left navigation menu.
  3. Go to Websites and Apps and select your project.
  4. Select the Manage SDK tab under the SDK settings section.

The tab displays a table of your project’s environments, each with its last SDK activity timestamp and the Force SDK refresh and Disable SDK controls for that environment. By default, these are Prod, Staging, and Dev, but you can edit them or add more.

Force SDK Refresh

The Force SDK refresh option instructs your SDK instance to update its current configuration settings immediately.

To apply an instant refresh:

  1. Navigate to the Manage SDK tab.
  2. Locate the specific environment, such as Prod or Staging, that you want to refresh.

  3. Click Force SDK refresh next to the environment name.

    Note: Each environment has its own refresh control, so you only need to refresh the environment that has changed.
  4. Click Confirm in the pop-up dialog box.

Once the refresh completes, Wingify displays a confirmation toast and updates the Last SDK activity timestamp for that environment.

Note: To maintain optimal performance, Wingify limits how often you can trigger this action. Once you click the button, the option remains disabled for 5 minutes before you can trigger another manual refresh.

Enable or Disable the SDK

The Disable SDK option serves as a remote kill switch to instantly halt Wingify operations in an environment. Use this when you need to stop flag delivery to an environment immediately, for example, if a rollout is causing errors in production.

To instantly halt Wingify operations:

  1. Navigate to the Manage SDK tab.
  2. Locate the environment that you want to control.

  3. Click Disable SDK to stop all experimentation and tracking. Wingify confirms the change with a toast, and the Disable SDK button for that environment changes to Enable SDK.

    Note: Disabling the SDK stops flag evaluation for every flag in that environment, not just one. Your application falls back to the default values coded into your flag checks until you re-enable the SDK.

  4. To resume normal SDK operations, click Enable SDK.

    Note: After re-enabling, trigger a Force SDK refresh once the cooldown allows it. This ensures your application picks up the latest configuration right away, instead of waiting for the next scheduled refresh.

Troubleshooting

Issue Possible Cause Recommended Solution
The environment displays SDK not deployed. The SDK has not been initialized in your codebase for that environment. Follow the SDK guide to initialize the SDK, then return to the SDK settings.
Flags are not updating in the application after a refresh. The application is using a cached SDK client instance that has not picked up the new configuration. Confirm the app is using the correct environment's SDK Key, then restart or reinitialize the SDK client.
Flags still show default values after clicking Enable SDK. The SDK client has not re-synced after it was re-enabled. Trigger Force SDK refresh once the cooldown allows it to force an immediate re-sync.

FAQs

  • What is the difference between disabling the SDK and using the shutdown function?
    Disabling the SDK keeps your application server running normally, but commands the Wingify SDK instance to stop evaluation logic and data tracking. The shutdown() function is a specific code method (available in .NET and Node.js SDKs) that technical teams invoke to gracefully close connections when an entire application container or server pod stops.
     
  • Does the Last SDK activity column show all tracking events?
    No. The Last SDK activity column displays the exact timestamp of the most recent manual force refresh action or the most recent automated update execution in that environment.
     
  • Is disabling the SDK the same as deleting my feature flags?
    No. Your flags, rules, and variations remain fully configured and available in Wingify. Disabling the SDK only stops that environment from fetching and applying them until you enable it again.
     
  • Do I need to redeploy code after re-enabling the SDK?
    No. Enable SDK restores configuration delivery without a code change. Trigger a Force SDK refresh afterward if you want the new configuration to apply immediately instead of on the next scheduled poll.

Need more help?

For further assistance or more information, contact Wingify Support.

Was this article helpful?

Return to top

Related articles