Task Reopens Due to Customized State Values Conflicting with OOTB Task State LogicIssue Order Management tasks automatically reopen or transition to unexpected states after successfully completing. Symptoms Tasks complete successfully and then reopen automatically.Tasks move from Closed back to In Progress.Tasks move from In Progress to Awaiting Information without a manual update.Activity history shows system-driven updates.The behavior occurs intermittently and affects only certain records. Facts The "Task Active State Management" Business Rule was identified in the transaction history when state changes occurred.The Business Rule references the out-of-box Script Include "TaskStateUtil."State choices on the affected task table had been customized from their out-of-box configuration.The updates occurred through system processing rather than direct user interaction.The available logs did not identify what initially set the Active field to true. Release Not release specific. Cause Customized task state values potentially conflicted with the out-of-box task state management logic. The "Task Active State Management" Business Rule uses state mappings through "TaskStateUtil." When the configured state values differ from the values expected by this logic, the Business Rule may update the task to an unexpected state. Resolution Review the customized task state values on the affected task table.Compare the customized values with the out-of-box state mappings used by "TaskStateUtil" and the "Task Active State Management" Business Rule.Identify and correct state values that conflict with the out-of-box task state management logic.Retest task closure and state transitions after aligning the state configuration.