Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions pages/docs/featureflags.mdx
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@efahk , concerns with posting this publicly? we keep getting customer/internal questions about this

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved the content itself. I think there is no harm in publicly stating this as it will be enforced anyway.

Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,10 @@ Mixpanel analytics downtime will result in suspended cohort membership refreshes
The latency of Feature flags API responses is usually on the order of milliseconds.
NOTE: Cohort membership is refreshed every 2 hours when targeting anything aside from 'All Users'/'All Entities' or 'Runtime Filters'. Therefore, new users or group entities entering cohorts may not be reflected in Feature flags API responses for up to that 2 hour period.

**Rate Limits**

Feature Flag APIs are rate limited to **500 requests per minute per IP address**. Requests exceeding this limit will receive a `429 Too Many Requests` response.

## Implementation
Feature Flagging is currently supported on a subset of Mixpanel client and server SDK's. There are two modes for using feature flags. Remote evaluation is available for both client and server SDKs whereas local evaluation is available for server SDKs.

Expand Down
Loading