VMware Aria Automation 8.18.x
When scaling up an environment and only using network tagging without Cloud Zone or Compute clustering filtering, the reservation calculations timeout and cause OOM errors within Aria Automation causing reservation filtering to fail and leave deployments in an inconsistent state, ultimately failing the request.
In addition to existing network tags, capability tag your compute or Cloud Zones and use constraints inside your blueprint to filter down to the appropriate cluster resource. This eliminates the large number of requests performed by the system when solely checking against networks across all your configured cloud accounts.