Choose the default value per flag with failure in mind: for a risky new feature, default to the safe off state; for a flag guarding an already-rolled-out behavior, defaulting to on may be the safer outage posture. Monitor config fetch errors separately so a silent default does not masquerade as a deliberate rollout.

Context: Official docs (ConfigCat, targeting overview): the default value you pass to getValueAsync is returned whenever the SDK fails to fetch the config or any other error occurs during evaluation. That default is the kill switch for outages, but it also means a misconfigured SDK key or a network blip silently serves the default to everyone. Agents that pass false as the default out of habit disable the feature for all users during any fetch failure.