https://waze.com/editor?env=row&lat=55.81586&lon=-4.37280&s=70622464&zoomLevel=16&segments=400717657
There have been roadworks with temporary traffic lights affecting both directions here for the past three or four weeks and it looks like a further two weeks to go. I drive this section of road every day and I have to add them via the waze app when I am driving in both directions.
It is not the full stretch it only lets me select the full segment. The area affected is as per below:
Approx. 55.815704, -4.375897 to 55.816881, -4.374444
Hopefully this is allowed.
As map editors, we can only record a road being open or closed. There is no facility for mapping traffic lights, whether permanent or temporary.
Waze routing should “notice” that the average speed along the road has dropped substantially due to the temporary lights, and factor this into its calculations. But if it’s still likely to be your quickest route, you’ll still get sent the same way.
You can use the app to make a “hazard” report. This will then appear for other users (provided they have the appropriate app setting enabled), and indeed for yourself on a repeat journey.
However, hazard reports get automatically wiped off after a period. By default, the period is fairly short. It will be extended if Wazers hit the “still there” button when it appears, and be shortened if they hit the “not there” button. The short default period is particularly annoyingly for potholes, which Waze seemly expects to be repaired in a matter of minutes. 
Ian
“Route speeds” shows an average speed of 10mph on the first section from the Hurlet to the Applecross Nursing Home turn, then 25mph - 30mph as you continue past the cemetery - so waze knows that section is slow.
Even so, the alternative routes are longer and slower because there are only a few places to cross the railway. You’d have to take Nitshill Rd then right into Wiltonburn Rd or Parhouse Rd. Or longer still, take Hurlet Rd towards Paisley then left into Grahamston Rd past Dykebar hospital.