Error calculating route on toll-free highway

[Esmolante]

Recently, OM insisted in marking a stretch of highway as a toll road that was not one (which led to a miscalculation of the best route).
I guess it's because one bridge on that stretch (77594573) did not have a toll-free limit specified, while the rest of the stretch did.
There had been no changes in OSM's history for years, and other OSM-based browsers did identify themselves as toll-free.
So could it be that OM assumes the absence of a toll tag as toll: yes?

[Esmolante]

I find the same error again on another stretch of toll-free highway (Specifically, this section: 40.67554, -4.11389). Organic Maps avoids it if the toll avoidance option is checked, even though in OSM it is correctly labeled and other OSM-based browsers do use it.
I consider this to be a bug that seriously affects the basic feature of a browser, which is to calculate the best possible route, and should be studied.