Flag status and last flag evaluation timestamps are incorrect for some flags

This incident has been resolved.

A fix has been implemented. Timestamps for any evaluations going forward will be properly recorded for all flags.

We have identified the cause of the issue and are working to get a fix out. Only flags that were returning a null or missing default evaluation value from the SDK since March 6 were affected.

We are investigating reports of incorrect "Last evaluated" timestamps and flags incorrectly reporting as "inactive". Flag evaluations data on the Flag Insights view is unaffected and showing correct data.

The flag delivery network and core feature management are both unaffected, so flags continue to be evaluated and updated without issue.