"State" field does not match "Incident State" field in an Incident recordIssue When the "Incident State" is updated in an Incident record, the below Business Rule should be triggered in order to update the "State" as well. Copy Incident State to Statehttps://<instanceName>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=27946b1b5f221000b12e3572f2b4776 Sometimes the above Business Rule does not get triggered causing the "State" and the "Incident State" to have different values.CauseOut of the box, the "Copy Incident State to State" Business Rule has a default "Order" value set to 1,000,000. A common scenario that would prevent the "Copy Incident State to State" Business Rule to be executed, is when you have another custom Business Rule that runs before the "Copy Incident State to State", that is also triggered during an incident update and that contains a "current.setWorkflow(false)" on the script. The "current.setWorkflow(false)" may prevent other Business Rules to get executed such as the "Copy Incident State to State" Business Rule. Please note that the setWorkflow may be set on a different Business Rule for another incident, and all the following incidents will get affected as current is not isolated.ResolutionIn order to resolve the issue, please review your custom Business Rule in order to prevent using current.setWorkflow(false). Scoped GlideRecord - setWorkflow(Boolean enable)