I figured it out. While poking around the control center, I noticed that Trusted Certificates conspicuously took about 10 seconds to open. This is about the same amount of time as the VAPI method...
See more...
I figured it out. While poking around the control center, I noticed that Trusted Certificates conspicuously took about 10 seconds to open. This is about the same amount of time as the VAPI method call took. Thinking that perhaps the method was trying to create a secure connection to vCenter, and perhaps was referencing the same certificate store to validate that connection, and perhaps was then suffering the same performance hit trying to enumerate the store, I created a workflow to clean up all the certificates I didn't immediately need. Those being the hundreds of certificates of devices left over from workflows which add them during execution because they're all self signed and needed for the runtime connection. Now the VAPI method completes almost immediately. So I'll just have to update all my actions which add certificates to remove each respective certificate after completion. Not a bad thing to do anyway for good housekeeping. Just never thought of it as necessary before.