I've seen this when there's a conflict with the TRC crossing numbering system. Try using a different numbering system for the crossings that's not as "close" to each other. It could also be a bug, but once I fixed a conflict due to merging in a route, the issue went away on my route.