VMware Cloud Community
KiwiDave
Enthusiast
Enthusiast
Jump to solution

Missing variables when running concurrent workflows

Hi,

We are running Orchestrator 4.1.1 and often run into a scenario where someone will run multiple instances of the same workflow at the same time (albeit with different input variables).

In some cases we are finding that workflows will lose variables (a common one is the AD object for a new computer which has been created) which causes the workflow to fail.

Is this something which has been experienced by others? Are we better off to ensure that we never run multiple instances of the same workflow at the same time?

Cheers,

Dave

Reply
0 Kudos
1 Solution

Accepted Solutions
cdecanini_
VMware Employee
VMware Employee
Jump to solution

This should not happen. If this is something you can reproduce by providing an example then you should file a support request so this can be investigated further and fixed.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter

View solution in original post

Reply
0 Kudos
3 Replies
cdecanini_
VMware Employee
VMware Employee
Jump to solution

This should not happen. If this is something you can reproduce by providing an example then you should file a support request so this can be investigated further and fixed.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
KiwiDave
Enthusiast
Enthusiast
Jump to solution

Ok, I will try and get this reproduced reliably and log a support request.

Thanks,

Dave

Reply
0 Kudos
KiwiDave
Enthusiast
Enthusiast
Jump to solution

For anyone encountering this in the future, disabling asynch on the offending task (in this case a VIX task) resolved the issue for me.

Reply
0 Kudos