Task state moves to Closed Complete when selecting Closed SkippedDescriptionWhen trying to set the state of an sc_task or task record to Closed Skipped, the task moves to Closed Complete instead.CauseThe out of the box task closer business rule is triggering when it should not due to other business rules setting the state field lower down in the order.ResolutionThe task closer business rule has 3 conditions that all need to be true to determine when it should run. 1. The task is inactive 2. The task is in an open state 3. The task is in a supported table If there is a business rule with a lower order than the task closer business rule that changes the state to an open state, this will trigger the task closer business rule since all 3 conditions are met. The task will be set to inactive if a user tries to set the state to Closed Skipped, the task would be on a supported table and will now be in an open state.To fix this, ensure that there are no business rules that run before the task closer business rule that updates the state field.Additional InformationFor information on the order of business rules and how they run in conjunction with other engines, please refer to our Execution order of scripts and engines documentation