UR's missing from Feed tab

Hello,
I am having this strange issue where UR’s aren’t coming up in my Feed.
They appear on the map, and I can click them and reply, however I cannot see them in the feed.
I have turned all scripts off, tried various browsers, did a Ctrl+F5, and tried in incognito.

Not sure what else to do!

Screenshot

2 Likes

Hi Alex,

Thank you for the report. Could you please send a permalink to the location, where you checked URs?

Best,
Nataliia

It’s a problem in all of my edit area…
But here is a permalink

Same here. The feed is empty in every edit area I have. Netherlands, Oman, UAE, Mosul (Iraq).

1 Like

Thank you Alex for the link. Could you please tell if you can see your recent drives?

Best,
Nataliia

Hi Gerard,

Thank you for the report. I have the same question for you, could you please check if you can see your drives?

Regards,
Nataliia

For me Drives are OK but the Feeds NOT
Screenshot 2022-11-04 150003.jpgScreenshot 2022-11-04 150021.jpg

Have you clicked on “Load More” at the bottom?

Yes did, and its still negative

Drives are showing just fine.

I know we had the same problem before where for a number of editors the URs disappeared.

Thank you Everyone for your replies. Do I understand correctly that the issue appears on both WME beta and Prod?

Regards,
Nataliia

The problem exists in production and in beta WME. Using Chrome I get the tabs “Issues, Drives, Area and Events” but in MS Edge I get the tabs "Feed, Drives, Area and Events"Issues vs Feed.png

1 Like

Thank you Stefan for your comment.

I have filed an internal issue for this. The team will investigate it.

Best,
Nataliia

Yes, all my drives are displaying correctly, and its occurring in Beta and Prod

Drives appear to display correctly for me in production WME and beta WME.
The Feed appears to display correctly for me only in beta WME.
The Feed appears empty for me only in production WME.

Browsers tested
Google Chrome 108.0.5359.22 (Official Build) beta (x86_64)
Mozilla Firefox 106.0.5 (64-bit)
Sample console log, from Firefox, dated 2022-11-05 (today/Saturday), and timestamps in US/Central Daylight Time (CDT) UTC-05:00

13:04:07.611 XHR GET https://www.waze.com/Descartes/app/Feed/Issues
[HTTP/3 500 Internal Server Error 84ms]

GET

Scheme https
Host www.waze.com
Filename /Descartes/app/Feed/Issues
Address 130.211.9.172:443
Status 500 Internal Server Error
Version HTTP/3
Transferred 1.05 kB (86 B size)
Referrer Policy strict-origin-when-cross-origin
Request Priority Highest

13:04:07.714 Uncaught (in promise) TypeError: t is undefined
refresh https://editor-assets.waze.com/production/js/app-4178dd58723ff26fc505.js.gz:1
promise callback*refresh https://editor-assets.waze.com/production/js/app-4178dd58723ff26fc505.js.gz:1
refresh https://editor-assets.waze.com/production/js/app-4178dd58723ff26fc505.js.gz:1
onRender https://editor-assets.waze.com/production/js/app-4178dd58723ff26fc505.js.gz:1
dispatch https://editor-assets.waze.com/production/js/third_party-5cbbce7443d16d79319b.js.gz:2
handle https://editor-assets.waze.com/production/js/third_party-5cbbce7443d16d79319b.js.gz:2
app-4178dd58723ff26fc505.js.gz:1:1106537

13:16:54.888 XHR GET https://www.waze.com/Descartes/app/Feed/Issues?lastIssueId=
[HTTP/3 500 Internal Server Error 100ms]

13:16:55.006 Uncaught (in promise) TypeError: e is undefined
loadMore https://editor-assets.waze.com/production/js/app-4178dd58723ff26fc505.js.gz:1
promise callback*loadMore https://editor-assets.waze.com/production/js/app-4178dd58723ff26fc505.js.gz:1
_onLoadMoreClick https://editor-assets.waze.com/production/js/app-4178dd58723ff26fc505.js.gz:1
dispatch https://editor-assets.waze.com/production/js/third_party-5cbbce7443d16d79319b.js.gz:2
handle https://editor-assets.waze.com/production/js/third_party-5cbbce7443d16d79319b.js.gz:2
app-4178dd58723ff26fc505.js.gz:1:1106974[color=#000000] [/color]

Example PLs
~Default NA/US location: https://waze.com/en-US/editor?env=usa&lat=40.73565&lon=-73.99078&s=549751619583&zoomLevel=12 (with all layers enabled except area managers)
(unavailable attachment: Screen Shot 2022-11-05 at 13.25.38.png)
Houston, Texas https://waze.com/en-US/editor?env=usa&lat=29.76043&lon=-95.36980&marker=true&zoomLevel=12 (tested with the same layers as above)
(unavailable attachment: Screen Shot 2022-11-05 at 13.17.08.png)

1 Like

Hi Everyone!

Could you please let us know if this has been fixed on your end?

We had some infrastructure issues over the weekend that should be now solved. New issues should appear normally in both prod. and beta.

Thanks in advance!
Maia

1 Like

Hi Maia,

The issue has indeed been solved for me! Thanks!

Edit: one caveat; I only get new URs. The old ones are not (yet) back.

Edit2: I spoke too soon. They’re gone again :frowning:

1 Like

Thanks for the feedback!

Are new issues appearing in the feed?

Best,
Maia

No. The feed is empty again, in prod & beta.

The Feed remains empty for me in WME production, without any scripts. WME beta displays normally for me.

When I click Load More in production WME the server responses appear to be the same as previously detailed, HTTP status code 500 (Internal Server Errors) from a GET request to “https://www.waze.com/Descartes/app/Feed/Issues?lastIssueId=”.