This is a known issue affecting VMware NSX for vSphere 6.2.x.
Currently, there is no resolution.
To work around this issue, update the Edge configured datastore as the current datastore either from the User Interface or using the following API.
For example:
Get https://181.126.111.111/api/4.0/edges/edge-39/appliances
Note: Do not make any change to the configuration and ensure to add the same configuration back from the GET body. This updates the configured datastore Appliance setting to the current state.
For example:
Put https://181.126.111.111/api/4.0/edges/edge-39/appliances