In the end, I was able to resolve this issue after making a small modification to a different area of the map. After the modification, the no go zone issue was resolved.
I’ve done the same last time. Now I have a patch mowed I don’t want mowed and the issue still pops up. I basically have to check the map each time it runs.
It’s only one extra step in the process of using Yarbo
Interesting. That didn’t happen to me. Once I made the one completely unrelated map modification, the no go zone issue disappeared and hasn’t come back (yet).