The new Waze Wiki, aka Wazeopedia, is now live at! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Known issues

From waze
Revision as of 16:11, 2 August 2012 by Alanoftheberg (Talk | contribs)

Jump to: navigation, search

Service Issues

Check for current known service issues on the Waze Status webpage.

Recent Fixes


Known Issues

Waze App

Please see the Waze App Bugs and Issues page for bugs and issues with the Waze app.

Website (Dashboard, Community)

Date Issue Description Workaround Status
2011-08-01 Foursquare integration is broken. Foursquare turned off their APIv1 functions, which Waze uses. Until Waze updates to use the new API, checking in via Waze will not be available.

The new API is available in Waze v3 and up.


Waze Map Editor

  • Always check waze status for the latest issues and information.
  • Papyrus is the internal name used for the next generation Waze map editor.
  • Papyrus uses the same live database as Cartouche, and therefore also has a separate instance for North America and World.
  • Even though they access the same database, Waze Map Editor has a small buffer database or tables between it and the real data so there are occasional lapses in proper road display and potential for different display between Waze Map Editor and Cartouche

In the table below, "Region" values are as follows:

  • All
  • NA (North America)
  • INTL (Global except for North America)
Date Region Issue Description Example Image/Link Workaround Status
2012-03-21 All "My places | Drives" archive is often displaying some drives incorrectly marked as "Yesterday" or "Today". + Open
2012-03-21 INTL If a lower-ranking editor (no AM) creates all segments, joined in a junction and a higher-ranking editor locks all of them, the segments' former author can still modify their connectivity arrows through the junction. Open
2012-03-05 All City layer does not update when city/state/country attributes are changed on segments. Open
2012-02-12 All Adding a new segment to an existing segment and panning while adding the new segment because it is longer than will fit on the screen, will cause the editor to duplicate the original segment and this will cause an error and will not save. Draw a short segment first and save, then extend the segment. Open
2012-02-12 All Cannot delete an unlocked segment last edited by a higher-ranking editor.

Location: Outside AM area, inside Editable Area Object: Unlocked segment

Previous edit by: Higher-ranking editor

Action not allowed: Deletion

Actions allowed: all others

Modify segment geometry. The segment can then be deleted. Open
2011-11-13 INTL Sometime, when saving edits (not necessarily to a roundabout), it will result in an error and the highlight will show the error on a roundabout in another country. + Undo some of the changes and try edits again. Possibly the undo is not necessary at all! Open
2011-09-07 All Very large landmarks "flip" their area covered at certain zoom levels.
Ocean Landmark


Land Landmark
Waze Map Editor was supposed to hide very large landmarks which are more than 2 degrees in width or height. This may or may not be happening, but as of 2011-10-13, examples of this are still visible. Resolved
2011-10-10 All Locked status and possibly other attributes do not appear to save. Locked status particularly, does not save. In general, this is resolved. There can still by sync errors which will cause this to happen sometimes, but it is not a systemic issue just related to the locked checkbox. Resolved
2011-09-22 All All save errors are generic, without specific guidance or spotlight on the error. Must progressively undo changes until the save goes through or undo all and do incremental changes and saves. Resolved
All Separating line checkbox is unavailable. Separating line will be not be added to the Waze Map Editor, and the display of the separating line on Primary Street road type will be removed. There is no use for this option. Pending
INTL Very few map problems appear. Map problem detection is being rewritten and very few map problems are currently available. As the new editor matures, more automated detection will be added. Resolved
INTL Map error "Missing Road" shows way too often and in places where there are very few GPS tracks. There is a flaw in the detection algorithm for this error which has been identified. A fix is supposed to go in by early November 2011. Resolved
INTL No map problems appear. Map problems have not yet been implemented on the World server. Use Cartouche. Resolved
All Cannot see Update Requests. Use Cartouche. Resolved
All Window space usage is not optimal. Too much wasted space and left details sidebar is too large. Current maximum viewable map area is set to maximize browser performance using Waze Map Editor, which utilizes the browser for more functionality that previous editor versions. This is not likely to be changed. Resolved
All NEW:2011/12/12: Allow all connections creates routing server connectivity the wrong direction on one-way or no entrance roads. This is called "reverse connectivity."
This function in Papyrus allows connectivity in all directions for all roads at the junction, regardless of the specified directionality of the roads.
Use cartouche to disable then enable turns in the junction to set the correct connectivity.
All Disallow all connections doesn't actually do that. This function in Papyrus disallows all connections for road directionality currently available. However, if any reverse-allowed connections are enabled, they are not disabled. To truly disable all connections, use Cartouche. Resolved
All Reverse connectivity is enabled when one-way roads are split in Waze Map Editor. Select the new junction and use the "Disallow all connections" function or keyboard shortcut, then individually all correct connections.

UPDATE 2012-02-27: Waze Map Editor beta now properly allows all connections according to connected segment directionality.

All When adding a segment which connects to the same segment twice (creates a loop), the first connection point does not split the first segment and create a junction node. Working as designed. NOT AN ISSUE. Before saving, move the first node of the new segment, and then move it back to where you want to first junction to be created. Papyrus will now split the original segment. Resolved
All Cannot add alternate names. Use Cartouche. Will be added to Waze Map Editor in the future. Open
All Yellow "add intersection" sign for crossing segments doesn't appear reliably. Segments must be set to the same level, country, state (where applicable) and city. For recently drawn or modified segments which now cross each other at the same level, you may need to use the Permalink to reload the current view. The Add Intersection icon should appear above the intersection when both segments are selected. Open
All Moving the free end of dead-end street while it is selected will disconnect it from its terminal junction. This causes routing to fail on this road. Move the end of a dead-end road by selecting the junction node at that end and moving it. Open
All A dead end road with no junction at the end will cause routing problems for the road as a departure point. When creating a new dead-end road in the editor, a junction is not automatically applied. Open


Region Issue Description Example Image/Link Workaround Status
All In general, there is a 650 mile/ 1047km restriction on navigation routes. Some locations may still be restricted to 200 mile/322 km routes. The client will usually display that it cannot do routes over 1000 miles, but the real limit is around 650. Open
World The icon display for roundabout directions are incorrect for countries that drive on the left. Open
NA The client does not display the name or give the proper verbal instruction for a ramp segment if the next segment is also a ramp segment. The clients receive information for screen and speech prompts from the routing server. The current state is somewhat by design in an attempt to minimize "Exit to <blank>" prompts, but when a ramp segment does have a name, it should display it. That part is a bug. Closed