I think this is a similar issue to #4972. We've got two Flipt 2.3.1 pods deployed in Kubernetes.

The scenario seems to be (using 2 fictional pod names flipt-pod-a and flipt-pod-b):

1. User creates feature flag via dashboard
2. 'create feature flag' API call gets load balanced to flipt-pod-a
3. flipt-pod-a updates the feature flag locally & pushes to Git
4. Browser is redirected to the page for that feature flag
5. 'get feature flag' API call gets load balanced to flipt-pod-b
6. flipt-pod-b returns a 404 since it hasn't sync'd new flag from git yet

A similar issue happens with other state updates. i.e. may toggle a feature flag and the UI shows a stale value because it gets routed to the opposite pod.