step 9 is filtering application gateway, however application gateway service is not filtered
as a result when pattern runs it has error lb service doesn't have relation to application gateway.
As in issue 1>, after both gateway and service are filtered, the public IP and private IP are not.
The merge at step: 17,18,20,21 are keep, not remove. As a result some invalid IPs are kept and used as service eventually, causing same error: service doesn't have relation to application gateway.
Set up and run discovery schedule for Azure service account that can trigger Azure Application gateway pattern
There is no known workaround for this issue. If you are able to upgrade, review the "Intended Fix Version" section below below to determine the versions that have a permanent fix.
If you have any question, please create a support case.