RITMs Created Without Workflow Attached IntermittentlyIssue Request Items are being created in the Production environment without the expected workflow being attached, causing them to remain in a waiting state and preventing fulfillment activities. Release Zurich Patch 12 and earlier, and Australia Patch1 through Patch3 Cause 1. The issue is caused by a known problem (PRB2035844) involving apparent scope stack corruption, leading to global code executing under an app scope.2. This corruption affects the workflow, preventing proper updates to the sc_request record and resulting in workflows not being attached to RITMs. Errors in the logs: GlideElement *** WARNING *** Error creating glide element of type: GlideElementWorkflowConditions in scope sys_script. Attempting to re-initialize.: GlideElementWorkflowConditions is not allowed in scoped applicationsThis error then appears several times in the transaction:ScriptEvaluator *** WARNING *** *Unexpected* - we are running some code in the public half of the sandbox, but without enforce security!: null Resolution Recommend upgrading to Australia Patch 5 or Zurich Patch 11, as these versions include the fix for the identified problem.