Notification not triggering on Incident after Flow has been CancelledIssue When using a Notification on the Incident [incident] Table you find it is not triggering even though the Flow has updated the Incident to meet the Notification Conditions.CauseThis can happen when the Flow Context is Cancelled while the "Update Record" Action is still executing. Even though the Incident [incident] Record Values get updated the cancellation will still mean that Business Rules and Email Triggers do not Trigger and therefore the Notification will not get sent as expected. Most likely a Business Rule is cancelling the Flow using the Flow API and it is getting triggered based on the Incident Update. (In this scenario the Flow is then Cancelled before the "Update Record" Action is Completed).ResolutionPlease ensure the Business Rule is not Cancelling the Flow Context until after the Notification Trigger. Alternatively you can remove the functionality that is cancelling the Flow Context.