How To Fix WL409 - Workflow '&' no. &: Element '_WF_Initiator' missing in workflow container

WL409 - Overview

• Message type: E = Error

• Message class: WL - Workflow: run-time messages

• Message number: 409

• Message text: Workflow '&' no. &: Element '_WF_Initiator' missing in workflow container

What causes this issue?

When the (sub)workflow '&V1&' (no. &V2&, step or definition no. &V3&)
was created, there was no initiator (element <ZH>_WF_Initiator</>) in
the workflow container.

System Response

The workflow was started without the element <ZH>_WF_Initiator</>.
This leads to problems if the workflow (or one of its subworkflows)
uses the element <ZH>_WF_Initiator</> as the agent of a task.

How to fix this error?

Make sure a binding has been defined for the element <ZH>_WF_Initiator
</> from the event which started the workflow to the container of the
workflow task '&V1&' (no. &V2&). The element <ZH>EVT_CREATOR</> of the
event container generally contains a user name or another
organizational unit which can be used for this binding definition.
When the workflow is started in dialog, this error should not occur
since the initiator is then set automatically by the appropriate
workflow transaction.
When a subworkflow is started, the initiator of the higher-level parent
workflow is used automatically.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WL409 - Workflow '&' no. &: Element '_WF_Initiator' missing in workflow container ?

  The SAP error message WL409 indicates that there is an issue with a workflow where the expected element _WF_Initiator is missing from the workflow container. This error typically occurs in SAP Business Workflow when the workflow is trying to access a variable or element that has not been defined or initialized properly.
  
  Cause:
  
  Missing Workflow Container Element: The workflow is trying to reference the _WF_Initiator element, which is not present in the workflow container. This can happen if the workflow was not started correctly or if there is a misconfiguration in the workflow definition.
  Incorrect Workflow Definition: The workflow definition may not have been set up to include the necessary elements, or there may be a mistake in the workflow logic that prevents the element from being populated.
  Workflow Initiation Issues: If the workflow is initiated incorrectly or if the initiating user does not have the necessary authorizations, the _WF_Initiator element may not be