A stop with a problem is marked on the list. Most of those marks are advice rather than a blockage — exactly one of them stops the route optimizing. Each warning below is one specific cause with one specific fix.

The two clients word these differently — the web app writes a sentence, the phone app writes a short label. Both are given, because you'll search for whichever one you're looking at.

	Severity	Blocks optimize	Fix in
Cannot geocode address	Red	Yes	The address, or the map pin
Transit area error	Red	No	The map pin
Invalid time window	Red	No	The arrival window's from / to
Cannot visit time window	Orange	No	The arrival window, or the stop's priority
Waiting time after arrival	Blue	No	Not an error — nothing to fix

Severity is the phone app's stop border colour, and says nothing about whether the route can be optimized. Each warning is detailed below.

The address couldn't be found

Web: "Location not found. Click to edit address or move the pin." App: Cannot geocode address

Routerra couldn't turn what you typed into a point on the map. Usually a typo, an incomplete address, or a place that simply isn't in the map data — new developments and rural addresses are the common ones.

The fix: correct the address, or place the stop by pointing at the map instead, which skips address lookup entirely. On the web app the warning itself is clickable and takes you straight to editing. In the phone app the banner isn't tappable — open the stop and edit it from there.

The address is outside the transit area

Web: "Location unreachable. Click to edit address or move the pin." — or "Location is outside of transit area" App: Transit area error

The address was found, but it isn't somewhere Routerra can route a vehicle to. Typically a pin dropped in the middle of a field, a lake, a pedestrian-only zone, or far enough from any road that there's no way to drive there.

The fix: move the pin closer to the road that actually serves the address. A delivery entrance round the back still needs a pin the router can reach.

This one doesn't block optimizing, despite the red border. It used to, and it was deliberately changed so that one unreachable pin can no longer hold up the whole route. Routerra will optimize around the stop and give you an order to drive; the warning stays on the stop until you move the pin, and the leg to that stop is the part you should expect to be wrong.

The stop can't be visited at the time you set

Web: "Cannot be visited at selected time" App: Cannot visit time window

The stop has an arrival window, and the route as it stands can't get there inside it. The window isn't wrong in itself — it just doesn't fit alongside everything else on the route.

The fix: widen the window, move the stop earlier using its arrival priority, or accept it and remove the window. See Stop settings.

The arrival window is backwards

Web: "Arrivel time ‘from’ must be before ‘to’. Click to update." App: Invalid time window

The from time is later than the to time, so the window describes no actual period. (The web wording has a longstanding typo — "Arrivel" — which is worth knowing if you're searching for it.)

The fix: open the stop and put the two times the right way round. If you meant a window that runs past midnight, that's supported — see Stop settings for how overnight windows work.

You are unlikely to see this one. The warning exists in both clients, but nothing on the server currently produces it, so in practice a backwards window shows up as the stop simply not being visitable rather than as this message. It doesn't block optimizing either way.

Waiting time after arrival

Web: "Waiting time after arrival" App: Waiting time after arrival, with the amount of time

This one is not an error. It's telling you you'll arrive before the stop's window opens and will be sitting there until it does. The phone app marks it blue rather than red for exactly that reason.

If you don't want the wait: widen the window's start, or let the optimizer move the stop later by changing its arrival priority. If the wait is fine — you're early for a scheduled appointment — leave it.

Optimize is greyed out because of a stop

If Optimize won't run and the reason given is that issues need resolving, look for a stop whose address couldn't be found — that is the only warning on this page that disables the button. A transit area error, a time window that can't be met, or a waiting time will all leave Optimize available, however alarming the stop looks. The wording is a catch-all, so it also covers a route with no start location address, which puts no mark on any stop at all; the other reasons a route won't optimize are covered in Optimize your route.

The map won't load

There's no dedicated recovery screen on the web app. Reload the page, and check your connection — the map is loaded from an external map service, so it's the first thing to fail on a weak network. If reloading doesn't help, try another browser or network before assuming it's your account.

The app can't get your location

This one is phone-only.

Routerra asks for foreground location only — while you're using it, never in the background — and it asks for a reason each time.

There are two separate moments it can ask, and they behave differently:

Quietly, when the app starts. Say no and it won't ask again. Nothing breaks; the app just doesn't know where you are.
Directly, when you press Use my current location. Say no here and you get Location Permission Required with a route through to Open settings, because at that point you've asked for something it can't do without permission.

If you said no earlier and want to undo it, you won't be asked again — grant it in your phone's settings for Routerra.