Hmmm, the plot does thicken..! Here's the thing, I didn't use the vCAC Designer to call the vCO workflow. I used the vCAC Extensibility Plugin in vCO to bind the vCO Workflow to the Machine Provisioned WF Stub (as well as select Blueprints). (See attached screenshot). Is this not the way I should've associated the vCO Workflow??

Do I need to perhaps remove the State Change Workflow and re-assign (due to a registering anomaly) or do I now need to manipulate the built-in WFStubMachineProvisioned in vCAC in order to ensure the ID (GUID) of the vCAC Machine being provisioned is passed as a "string" instead of a native "object"..?? That doesn't seem right, does it??

Thx Ronald..

Ron