vRO is trying to run two instances of the same workflow at the same time. One runs and one fails.

[dalehassinger]

Has anyone ever seen an issue where vRO is trying to run two instances of the same workflow at the same time.  One runs and one fails. The one that fails the error is "The operation is not allowed in the current state".

Example is two different uses submit a BluePrint to run at the exact same time. One will complete and one will fail.

If the workflow is run 100 times but never close together in time, they will always complete OK.

[eoinbyrne · Accepted solution]

Which version is this on and what is the context (XaaS, EventBroker). Also, is this a custom workflow or an OOTB one?

Usually, vRO can happily run many instances of the same workflow as long as there are no shared resources. If there are shared items you should look at using workflow locking

[dalehassinger]

vRealize Orchestrator

7.6.0.15624332

Xaas

Combination of OOTB and Custom Workflow.

I will take a look at Workflow Locking.

[dalehassinger]

I added Locking to my workflow and that seems to have fixed my issue.  I don't like the fact that before vRA 7.6 HF 5 and the latest version of vRO I did not have to do this.  Almost like a bug was introduced and this is just a work around. Thanks for the help.