Odd Behavior with HTTP node since upgrade

I have been using the a flow that takes address information from our CRM and sends it to a weather site (weatherbit.io) and retrieves the weather information. It has always worked fine until I upgraded. I was passing the address information stored in a flow variable as msg.payload to the HTTP node to "GET" the appropriate location. I now starting getting an error in the HTTP node as invalid parameter. I commented out the msg.payload information and it works fine. Thing is it is using the correct address even though I am not sending the address to the HTTP node. It is just in the flow variable. When I say it works fine, I mean when the address changes so does the weather report and it reports for the correct city. But I am not loading the address information into the GET request. Any idea how or why the HTTP node would pick up something directly from a flow variable?