Azure Spring Boot feature flags not refreshed on cache expiration

TL;DR

With cache-expiration configured (e.g. every 1 second for testing), feature flag values toggled in the Azure portal are never refreshed in a Spring Boot app using spring-cloud-azure-feature-management-web.

Steps

1. With cache-expiration configured (e.g. every 1 second for testing), feature flag values toggled in the Azure portal are never refreshed in a Spring Boot app using spring-cloud-azure-feature-management-web. The FeatureManager is autowired and other configuration refreshes fine, but flag values stay stale.
2. The feature-flag naming issue behind this was fixed in the latest spring-cloud-azure-feature-management release, upgrade the library and the refresh works. One limitation confirmed by the maintainers remains: feature flags cannot currently be served from multiple App Configuration stores, since flag storage assumes a single store. That part was split into a separate feature request.

Expected: The feature-flag naming issue behind this was fixed in the latest spring-cloud-azure-feature-management release, upgrade the library and the refresh works.

When to use

You are seeing this: The FeatureManager is autowired and other configuration refreshes fine, but flag values stay stale. Use this skill when you run into "Azure Spring Boot feature flags not refreshed on cache expiration".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

With cache-expiration configured (e.g. every 1 second for testing), feature flag values toggled in the Azure portal are never refreshed in a Spring Boot app using spring-cloud-azure-feature-management-web.

In the thread Azure Spring Boot feature flags not refreshed on cache expiration, the question was: With cache-expiration configured (e.g. every 1 second for testing), feature flag values toggled in the Azure portal are never refreshed in a Spring Boot app using spring-cloud-azure-feature-management-web. The FeatureManager is autowired and other configuration refreshes fine, but flag values stay stale. The verified resolution: The feature-flag naming issue behind this was fixed in the latest spring-cloud-azure-feature-management release, upgrade the library and the refresh works. One limitation confirmed by the maintainers remains: feature flags cannot currently be served from multiple App Configuration stores, since flag storage assumes a single store. That part was split into a separate feature request. Original discussion: https://vectle.com/threads/thr_dGx0rMl6VYL3aTqFsjCN0w