Errors while submitting Terraform template: java.lang.NullPointerException - Could not load credentials. Cannot process the request. - 'null'DescriptionWhile submitting the Terraform template on the Cloud Portal, the below error is traced in CAPI trail logs: java.lang.NullPointerException Mid server logs: 2023-09-01 09:39:32 ERROR (Worker-Standard:APIProxyProbe-7ec3344987c139d0673065f30cbb3547) [APIProxyProbe:119] Could not load credentials. Cannot process the request. - 'null'2023-09-01 09:39:33 WARN (Worker-Standard:APIProxyProbe-7ec3344987c139d0673065f30cbb3547) [RhinoExceptions:285] org.mozilla.javascript.EcmaError: Cannot convert null to an object.Caused by error in Ad hoc script 'TerraformProviderCredentialResolver' at line 26Release or EnvironmentAnyCauseIncorrect Mid-Server SelectionResolutionOnce you rectify this error. If you are still seeing this kind of error.Need to validate the credential record which is being picked by the Terraform template. You can see that the credentials which are passed in the request are limited to specific mid server and the mid used for processing the request is not in the list . Mid Server logs : at com.snc.cmp.mid.probe.APIProxyProbe.probe(APIProxyProbe.java:114) at com.service_now.mid.probe.AProbe.process(AProbe.java:154) at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:131) at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20) at com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:649) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) If the credential record was pinned with only a few sets of mid servers, we can see the issue.Rather than that, we can see "ALL" on the credential record to avoid this issue. The best suggestion to overcome this issue : 1. Rather than making credentials specific to some mid-servers, make it available to all the mid-servers This way, whichever mid-server is picked up for processing the request will have access to the credentials. 2. Or we can make sure that only the mid servers whitelisted in the credentials page have the capabilities to process this terraform provisioning request and discovery for that VMware resource. This way no other mid-server will get picked up that doesn’t have access to credentials which might cause the issue later in the processingAdditional Information https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/mid-server/concept/c_MIDServerSelector.htmlhttps://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/mid-server/task/override_mid_server_selector.html