Unexpected Workflow Triggering Incident Creation Due to Business Rule ConditionsIssue A workflow is triggering unexpectedly, resulting in the creation of multiple incidents—even though the trigger conditions appear unmet.The impacted flow is "CC uCMDB – AppSvc Demise", and the incidents are being generated with the short description: "Application Service Demise Automation Failure".ResolutionTo stop further unintended incident creation: Review and refine the logic and conditions within the custom business rule ("Update MAS Ops to Retired - Non Operational") to ensure the flow triggers only under the intended circumstances.Investigate how the business rule sets the operational status of the mapped application service to 12 (Retired – Non-Operational), which in turn triggers the flow.Use the system logs and flow context records to identify and validate triggering behavior (e.g., see incident INC49590303 and its flow context).Adjust the business rule’s criteria to prevent unnecessary executions of the flow.