TBTR issues?

Are there any known issues with Waze not honoring TBTRs? I have a UR where it seems that Waze directed a user through a TBTR in the middle of its timeframe.

https://www.waze.com/editor/?env=usa&lon=-122.11523&lat=37.36840&layers=1924&zoom=5&segments=5344774&mapUpdateRequest=4825651

Yes there are. For instance if you have your routing type set to shortest, it seems TBTRs are completely ignored.

The reporter said his app was configured for Fastest. https://www.waze.com/editor/?zoom=5&lat=37.374613&lon=-122.118412&mapUpdateRequest=4825651&env=usa

I’ve gone ahead and forwarded this example to waze.

Like the reporter, waze staff can not currently route through the TBTR. They have a similiar case on a different server and are looking for a recent example on the NA server that they can reproduce.

So at this point I don’t think we can do anything further for this UR. However, if anyone has current examples of routing through TBTRs we should report them to waze.

Thanks for the effort!