Editing Private Environment Values Doesn't Invalidate Private API Deployment Status

[cranthoncodes]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

When updating environment values marked as private and then deploying the app to production, stale values continue to be used.

Expected Behavior

When updating environment values marked as private, the "Deploy Private APIs" page should show as "Out of Date", so that the developer knows to redeploy.

Steps to Reproduce

1. Create an environment value marked as "private"
2. Use that value as part of a private API call
3. Deploy
4. Change the value

Expected: The "Deploy Private APIs" page shows "Out of Date"
Actual: The "Deploy Private APIs" page still shows "Deployed", which is incorrect since the values have changed

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT40iPLqw5NOmN9G1pSJcsdanmU5Jj86a7s/kOtBaCgoIYyuOpl/evWldhNuXengdFVAMESmmkAew+yLjvPtG+0pGE6YfNlSzJNibQzjTjqjQZOBC4eWWGpBHdFNBW2Py6WFrQhAHM9iSV417TmYA+m/a3fAJZTvIlFISq/LZO4=

Visual documentation

Environment

- FlutterFlow version: v6.5.23 (released Feb 19, 2026)
- Platform: Web
- Browser name and version: Chrome 144.0.7559.133 (Official Build) (arm64)
- Operating system and version affected: macOS Tahoe 26.2

Additional Information

No response

[Alezanello]

Hello!!

Thanks for raising this. This is not a bug, but I understand your point and will treat it as an enhancement request.

Currently, the API and Cloud Functions deployment status changes to "Out of Date" only when there are explicit modifications to the code, request body, or URL. Changes to environment variables do not trigger this status at the moment. While it would make sense for those to be connected, this behavior is expected for now and therefore not considered a bug.

I’ll go ahead and create an internal enhancement request to evaluate this improvement. In the meantime, I’ll close this issue to keep the GitHub issue tracker focused strictly on reproducible platform bugs.

Thanks again for the suggestion!