# Routing issue with option "strict navigation"

**URL:** <https://forum.kurviger.com/t/routing-issue-with-option-strict-navigation/3250>\
**Category:** App\
**Tags:** problem\
**Created:** [May 18, 2020, 9:19am UTC](https://forum.kurviger.com/t/routing-issue-with-option-strict-navigation/3250 "2020-05-18T09:19:54Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\
**Post date:** [May 18, 2020, 10:37am UTC](https://forum.kurviger.com/t/routing-issue-with-option-strict-navigation/3250/12 "2020-05-18T10:37:07Z")

</div>

> [@Tom](#):
>
> Yes I did this to switch from navigation into overview… I didn’t think that this stopps the actual route completely. I thought this can be used all the time to see the route as a whole as a orientation where I am.

Strict navigation is already explained many times…  
It expects to begin near start and pass waypoints in order.

With flexible navigation modes can exit / resume route anywhere.

> [@Tom](#):
>
> If this is the reason why that happened, then I find that dangerous and not intuitive.

No comment.

> [@Tom](#):
>
> Why then not handle the navigation button automatically as a pause and resume button when the option strict routing is enabled?

Because it’s already discussed [elsewhere](https://forum.kurviger.com/t/app-pause-resume-navigation/3184) in forum?

> [@Tom](#):
>
> I can send you the video how I cursed a bit around 🙂

And then I could remove strict navigation from the app. 🙂

---

_[View the full topic](https://forum.kurviger.com/t/routing-issue-with-option-strict-navigation/3250)._