[backport cloud/1.33] cloud: increase feature flag polling interval to 10min (from 30s) #7111
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
) Increases the `/features` endpoint polling interval (runtime config polling) from the current 30 seconds to 10 minutes. ## Background The polling was originally added for two main purposes: 1. Server alert badges 2. Extra assurance that states are synchronized between frontend and backend However, both of these use cases are not critical: - Server alert badges are unlikely to be needed in practice. WebSocket (WS) can be used eventually as an alternative - For synchronization, the system should be redesigned to be explicit about marking client state as stale, or use WebSocket/Server-Sent Events (WS/SSE) on a per-data basis rather than polling for the entire feature flag set ## Motivation The reason to reduce polling frequency is that per-user feature flags are being added, which will make `/features` endpoint handling significantly heavier. The endpoint will no longer just return static JSON with high cache age, making frequent polling more costly. ## Future Considerations - Eventually migrate server alert badges to use WebSocket - Design a system that explicitly marks client state as stale when needed - Consider using WebSocket or Server-Sent Events for targeted data updates instead of polling entire feature flag set ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-7100-cloud-increase-feature-flag-polling-interval-to-10min-from-30s-2bd6d73d365081dfa8abeec901d0d975) by [Unito](https://www.unito.io) --------- Co-authored-by: Alexander Brown <[email protected]>
dosubot
bot
added
the
size:XS
🎨 Storybook Build Status✅ Build completed successfully! ⏰ Completed at: 12/03/2025, 01:05:20 AM UTC 🔗 Links🎉 Your Storybook is ready for review! |
🎭 Playwright Test Results❌ Some tests failed ⏰ Completed at: 12/03/2025, 01:23:33 AM UTC 📈 Summary
📊 Test Reports by Browser
🎉 Click on the links above to view detailed test results for each browser configuration. |
christian-byrne
approved these changes
Dec 3, 2025
Contributor
|
Tests failing due to version compat toast warning. Will be fixed on future versions when backporting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #7100 to
cloud/1.33Automatically created by backport workflow.
┆Issue is synchronized with this Notion page by Unito