Getting errors for first minute when Associating Message Processor with new environment

[#1]

When associating a Message Processor (MP) with a new environment with using below API call, I'm seeing "Unable to identify proxy.." errors in Message Procssor logs for about the first minute. These errors hang around until Apigee has deployed all 80+ proxies from that environment onto new MP. I'm wondering why would Apigee route messages to a MP when it is not ready to receive traffic? I need to eliminate these errors and am not sure how.

https://apidocs.apigee.com/management/apis/post/organizations/%7Borg_name%7D/environments/%7Benv_nam...

ENV: Edge Private Cloud 4.16.09

[#2]

According to Apigee this is a known issue in 4.16.09 and is fixed in 4.17.x.