2 people reported

All time, since Jul 16.

Bad flag filter breaks /flags (500)

“One unparseable property filter in one flag stops flag evaluation for the whole team.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/posthog/issues/8062/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

One unparseable flag filter makes /flags return 500 for whole project. The flags service parses a team's flag payload as one unit; e.g. a numeric flag-dependency key accepted by the REST API.

Is this your bug?

File my report
Where
Feature flag evaluation
Error text
Failed to parse flag configuration data. This may indicate a misconfigured feature flag. Please check your flag definitions or contact support.

Original reports2, newest first

  1. fix(flags): one unparseable property filter takes down flag evaluation for the whole team#98879
  2. Feature flag API accepts a numeric flag-dependency key, but /flags then returns 500 for the entire project#71795

Do you work on PostHog?

Claim its RAP Sheet to see what your users report and answer them in one place.