Customer would have the capability to add/remove valid or invalid prefix. This issue will be fixed in upcoming HCX release.
Workaround:
Review the cloud HCX web.log and remove all the invalid prefix from HCX UI.
Log Snippet for reference :
admin@hcx [ /common/logs/admin ]$ grep "BAD_REQUEST" web*
web.log:2024-01-24 18:02:42.512 UTC [https-jsse-nio-8443-exec-8, Ent: HybridityAdmin, , TxId: TxId: 2e01a833-6ee6-41a6-8ee2-f2cf434b45af] ERROR c.v.h.n.util.NetworkExtensionUtils- Failed to create prefix list for tier0 TNT43-T0 policy routes. Response: {"status":"failure","statusCode":400,"details":"","result":{"httpStatus":"BAD_REQUEST","error_code":503041,"module_name":"Policy","error_message":"Invalid network CIDR 192.168.0.0\/1."}}