'State model - Can change state?' cancels change State update by Workflow or other scriptsIssue 'State model - Can change state?' cancels change request State update by Workflow or other scripts. Typical symptoms: Workflow shows that update change request State is complete, but the change request State is not changed. And there are usually logs showing 'State model - Can change state?' business rule aborted change request update transactions.ReleaseAllCause'State model - Can change state?' business rule enforces the change request State changes, it only allow state changes as the following Documentation described: https://docs.servicenow.com/csh?topicname=c_ChangeStateModel.html&version=latest https://docs.servicenow.com/csh?topicname=normal-standard-emergency-states.html&version=latest It is actually expected that the 'State model - Can change state?' business rule cancels the change request update, if the update doesn't follow the above State Model.ResolutionThis is expected behaviour. Each Change Request State change needs its separate update. E.g.: in Normal Change Request, from "Authorise" State, the Change Request can only be change to "Scheduled" State in one transaction. If the workflow design, or any other script, sets the change request from "Authorise" to "Scheduled" then immediately set the change request to "Implement" in the same transaction, the 'State model - Can change state?' business rule will see the transaction is trying to update the change request from "Authorise" to "Implement", then cancel the update. The workflow design must follow the State Model as well, and make sure each State change in its own transaction.