My guess is you are experiencing same issue as in Node inexplicably red.
To re-hash, the completion of nodes is based on one of the GPS points recorded in your run needing to be within 25 meters of a node on the street in CS. If your device struggles with satellite connection (ex: in tunnel, around tall buildings, etc) at a certain point, it won’t be able to record any GPS points for a short period. This leads to straight lines being drawn between when it last had connection to when it regained connection. That straight line may go through nodes but technically there are no GPS points that were close to the node.
Looking at your Preysnar run, it is a straight line from one side to the other. Based on the activity title, it sounds like you manually created a map and uploaded it. If that’s correct, I’m assuming you made one point at the start the street and then another point at the other end of street and thus you get a dead straight line. All the nodes in the middle of the street wouldn’t be close to either of the “fake” GPS points you added to your run and thus wouldn’t be marked as completed.
Looking at your Bayberry run that also looks like to be a manufactured run cause of how straight some of the lines look. I drew arrows where it looks like “fake” GPS points were clicked as there are subtle adjustments to the straight lines at those points.
If these both were manufactured map runs, then you would need to correct the original source that created the runs. You’d also have to do pretty the same workflow as How to edit a run from Garmin in order to get the new run processed. If you plan to have more manufactured map runs like this in future, you’ll need to add more GPS points to follow the street curves as that is where the nodes will be. In addition, even long, dead straight streets may have nodes in the middle of them so include a couple GPS points there as well.