Feature flags limitations

Forge Feature Flags is now available as part of Forge Early Access Program (EAP). To start testing this feature, sign up using this form.

Forge Feature Flags is an experimental feature offered to selected users for testing and feedback purposes. This feature is unsupported and subject to change without notice. Do not use Forge Feature Flags in apps that handle sensitive information and customer data. The Feature flags EAP is fully functional in development, staging, and production environments.

Note: Feature flags are not available in Atlassian Government Cloud or FedRAMP environments. See, Limitations.

This page outlines the current limitations of Forge feature flags during the Early Access Program (EAP).

Current EAP limitations

Current limitations

No client-side SDK - Feature flags are only available in Forge functions (resolvers, triggers, and backend code). Client-side evaluation in Forge UI is not supported during EAP.
No analytics or evaluation metrics - Cannot track feature flag evaluation success/failure rates
No scheduled rollouts - Cannot set up time-based staggered releases (e.g., 30%, 40%, 30% over three weeks)
No experimentation - Cannot conduct A/B/C tests with feature flags
No cross-app management - Cannot manage feature flags across multiple apps from a central location
Manual percentage updates - Must manually adjust percentage rollouts; no automated progression

Performance constraints

Flag evaluation latency - Feature flag initialization may add latency to app startup
Rate limiting - Feature flag API calls are subject to standard Forge API rate limits
Caching limitations - Feature flag states are cached; changes may take time to propagate

Management constraints

Resource	Limit	Description
Access	Admins only	Only app administrators can create, edit, delete, disable, or enable feature flags
Feature flags per app	10	Maximum number of feature flags that can be created per app
Rules per feature flag	10	Maximum number of targeting rules per feature flag
Conditions per rule	10	Maximum number of conditions that can be defined per rule
Values per condition	100	Maximum number of values per condition (e.g., user IDs, attributes)

Atlassian Government Cloud

Feature flags are not supported in Atlassian Government Cloud or FedRAMP environments during EAP.

If your code uses the Feature Flag SDK, the SDK will gracefully evaluate to the default value and will not break your application code.

The following constraints apply:

Feature flag creation, management, and evaluation are not available to tenants in Atlassian Government Cloud environments
Developer Console access and feature flag lifecycle actions (create, edit, delete) are not available from government networks/environments
Not supported in any FedRAMP environments

Next steps

Overview - Learn about feature flags capabilities
Quick start guide - Get started with your first flag
Tutorials - Build apps with feature flags step-by-step