Hey @finid, sorry for the delay, quite a few of us were out at lunch. I was under the impression the conclusion of this issue was that we need to suss out making this message more `INFO`rmational? As opposed to an error message? This shouldn't be something stopping up your deployment...