Wrt. logging, check /var/log/vmware/vco/app-server/scripting.log
Thanks, will check that out.
The only thing I see from that log is an attempt to resolve the vCenter VM from the vCAC item. It looks like that runs pretty much immediately. One thing worth nothing is that the delay seems to only affect the first time you run the action. For example the first time I ran action X the spinning icon literally went for 5 minutes before loading up the form. Cancel out and run it again and it only spun for a few seconds. Even after logging out and back on the delay is reasonable. It's almost like something get's cached after that first load, I don't fully get what though.
Is your DNS configured correctly on IaaS and vRA appliance?
Yes, I think I've narrowed the issue down to the vCenter plug-in, but I'm really curious why others aren't running into the same problem. The first time an XAAS actions runs for the day in server.log you see the error below. That error loops through every single VM in the vCenter and the XAAS page doesn't actually load in the UI until that's complete. This pattern seems to repeat every 4 hours, it's almost like the info gets cached and then the cache expires 4 hours later and runs again.
[ObjectUpdateParser] assign disabledMethod ->
java.lang.RuntimeException: java.lang.IllegalStateException: Cannot find managedMethod with name: UpgradeToolsFromImage_Task