---
schema_version: "1"
id: f943a69c8d0c3392a4ddce6560d348216e944c63aed50473fb0678c35ff34ea4
title: Considerations for Feature Management
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/fma/fma-considerations.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/fma-considerations.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: d251b9171816065e48d8fcae67b0fbcaec2cea048194b158ed79bc28242816a1
products:
  - Second-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Considerations for Feature Management

Keep these considerations in mind when working with feature parameters.

- After a feature parameter is included in a promoted and released package version, we recommend that you only edit the value field located in LMO-to-subscriber junction objects.

  Modifying or deleting other fields or records related to feature parameters, including the data flow direction, may cause the FMA to stop operating correctly.

- Don’t use the LMO to create or delete feature parameters.
- When you update LMO-to-subscriber values in your LMO, the values in your subscribers’ orgs are updated asynchronously. This process can take several minutes.
- When you publish a push upgrade to your managed package, feature parameters in your LMO and your subscribers’ orgs are updated asynchronously. Creating and updating the junction object records can take several minutes.
- When the Apex code in your package updates subscriber-to-LMO values in your subscriber’s org, the changes can take up to 24 hours to reach your LMO.