Hello wreedMH,
Not sure what you did there but that object selected looks somehow be FTT=0, with default Storage Policy (SP) applied but no absent/degraded components, assuming the default SP was not changed to FTT=0
It also appears to have improperly unconfigured stretched-cluster too as it still referencing 'Preferred' Fault Domain.
The first thing to do is verify that all 3 nodes are clustered properly and not in vSAN-level Maintenance Mode, both of which can be checked via SSH to a host using #esxcli vsan cluster get.
Look in the Health check of the cluster for indications of this also (e.g. partitioned cluster).
If all 3 nodes are clustered then verify can create FTT=1 Objects (there is a proactive VM creation test), if this is okay then reapply the default SP to the Objects to make them FTT=1 (or apply a new identical SP), this can be done either via the SP menu or directly on a VM/Disk (right-click and select policies or Edit Settings then change per disk etc.).
Bob