Error “currentWorkflow is null” observed during deployment due to missing workflow reference

Products

• VCF Automation

Issue/Introduction

In VCF Automation 9.0.2 deployment requests may fail during execution. The failure occurs because a workflow in VCF Operations Orchestrator contains a reference to a workflow item in workflow schema that no longer exists.

Failed to process ebs event: SubscriberID: service-account-vra-gateway-serviceaccount, RunnableID: <RunnableID> and SubscriptionID: <SubscriptionID> failed with the following error: Workflow run <Workflow-run-ID> completed with error [Cannot invoke "ch.dunes.model.workflow.Workflow.loadContent()" because "currentWorkflow" is null]

Environment

VCF Automation 9.0.2

Cause

A missing workflow item reference in the workflow schema prevents VCF Operations Orchestrator from processing the workflow, causing the deployment to fail.

Resolution

Remove or correct the missing workflow item in the workflow schema:

1. Log in to the VCF Operations Orchestrator user interface.
2. Locate and open the workflow that is failing during deployment.
3. Review the workflow schema and identify and re-add any missing workflow items as required.
4. Save the workflow.
5. Retrigger the deployment or re-run the workflow.