Discovery configured with a Load Balanced MID cluster is failing due to new business rule 'Restrict record creation for other mids'DescriptionIn Vancouver release, Discovery using a schedule configured with a Load Balanced MID cluster results in certain patterns failing to launch with an error message - Error while execution pattern "<Pattern Name>". This is due to below business rule preventing MID user A from being able to create output records for MID user B when logged in as different user. Restrict record creation for other mids - https://<instance_name>.service-now.com/sys_script.do?sys_id=23176a40777261103406f24a8c5a996dSteps to Reproduce Create a Load Balanced MID server ClusterCreate a Discovery Schedule configured to execute using the MID Server ClusterObserve that sometimes certain patterns will fail to execute with generic error 'Error while execution pattern "<Pattern Name>"Note: This issue can also occur during auto-select MID server. This will lead to the scheduled discovery to stop from execution and will also see an error message - “Access Denied. MID user:”WorkaroundThe issue is fixed in Vancouver Patch 5 and is available for upgrade.If you are unable to upgrade anytime soon, please follow the steps to apply the workaround that will update the Business Rule "Restrict record creation for other mids " and will provide the relief. Use either of the steps below - Modify the condition of the business rule - On the navigation filter type - sys_script.LISTSearch with sys_id contains "23176a40777261103406f24a8c5a996d"Set the condition to: current.state == "ready" && current.topic == 'Command' 2. Users should have both "admin " role to perform below action. - Import the update set "sys_remote_update_set_dd8259e20cb6b550f8778b6c4da37a20.xml" file - Commit the update set. This file will update the Business Rule "Restrict record creation for other mids". Make sure the Business Rule is updated and ensure the issue is resolved. Related Problem: PRB1711976