# "The endpoint of a sidewalk or pathway is inside a no-go zone" on 3.14.1

**URL:** <https://forum.yarbo.com/t/the-endpoint-of-a-sidewalk-or-pathway-is-inside-a-no-go-zone-on-3-14-1/7271>\
**Category:** Support & Solutions\
**Created:** [August 15, 2026, 1:23pm UTC](https://forum.yarbo.com/t/the-endpoint-of-a-sidewalk-or-pathway-is-inside-a-no-go-zone-on-3-14-1/7271 "2026-08-15T13:23:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kinglerch](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/kinglerch/32/489_2.png) [@kinglerch](https://forum.yarbo.com/u/kinglerch)\
**Post date:** [August 15, 2026, 1:23pm UTC](https://forum.yarbo.com/t/the-endpoint-of-a-sidewalk-or-pathway-is-inside-a-no-go-zone-on-3-14-1/7271/1 "2026-08-15T13:23:19Z")

</div>

Having this error with 3.14.1. It happens randomly, which I think means the cause of the problem is the path offset algorithm is placing the offset path into a ngz. I can’t prove this because THE SOFTWARE REFUSES TO SAY WHICH PATH OR NGZ IS THE ISSUE SO I HAVE TO GUESS but otherwise, I can disable ngz or adjust path settings, and make it go away, at least temporarily.

The other issue is that changing pathways is now painful because once a pathway is selected and shown on the map, the pathway list is reset. So finding the correct pathway and making changes is sure to make you dizzy and take way longer than necessary.

---

<div class="post-metadata">

**Author:** ![ben.karrow](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/ben.karrow/32/3989_2.png) [@ben.karrow](https://forum.yarbo.com/u/ben.karrow)\
**Post date:** [August 15, 2026, 1:40pm UTC](https://forum.yarbo.com/t/the-endpoint-of-a-sidewalk-or-pathway-is-inside-a-no-go-zone-on-3-14-1/7271/2 "2026-08-15T13:40:51Z")

</div>

Agreed. Once you click the error it should take you to the culprit(s).

---

<div class="post-metadata">

**Author:** ![jondorothy922](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/jondorothy922/32/233_2.png) [@jondorothy922](https://forum.yarbo.com/u/jondorothy922)\
**Post date:** [August 17, 2026, 2:30am UTC](https://forum.yarbo.com/t/the-endpoint-of-a-sidewalk-or-pathway-is-inside-a-no-go-zone-on-3-14-1/7271/3 "2026-08-17T02:30:38Z")

</div>

Yes, it’s very annoying when it fails to load map and just says ngz error. If it would show the area / highlight issues the would be very nice compared to searching the whole yard and guessing where the issue is…

---

<div class="post-metadata">

**Author:** ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)\
**Post date:** [August 17, 2026, 9:31am UTC](https://forum.yarbo.com/t/the-endpoint-of-a-sidewalk-or-pathway-is-inside-a-no-go-zone-on-3-14-1/7271/4 "2026-08-17T09:31:05Z")

</div>

Hi there, could you please submit a support ticket regarding this issue so our support team can further investigate and confirm the root cause?

Also, your suggestion about identifying the problematic pathway or NGZ directly is very helpful. We would like to address the issue from the root cause, but I will also share your feedback with our product team for further consideration to improve the troubleshooting experience.