Thanks for correcting me on the TSB situation. I'd also like to add, as a one-time service writer, it is of utmost importance to ask questions, when does this happen, get very detailed with the customer; but unfortunately, now that customer service reps handle scheduling - and most know nothing of any depth about cars, even asking them at the time of scheduling an appointment to make notes about when the problem occurs will never happen. But getting this information helped me to get praised by techs because they didn't waste time trying to duplicate a problem and could find it much more easily as they knew where to start in duplicating the customer's concerns.No, there is no TSB (technical service bulletin) for this. But yes, technicians should search for a TSB every time.
There is another step when the tests/diagnosis in workshop manual is not leading to a solution. Technicians can contact a field service engineer. Before doing that, techs can search symptoms for reports describing other people's contacts w/ field service engineers. That's where I found info about this issue.
And you are very right. They probably didn't take it on a long-enough test drive.
In most cases like that, having the someone drive with you to make sure they understand what the problem you have actually is is important.
Providing this information to the tech is much better than what I used to get as a tech. "Check for rattle." "Customer states there is a squeak." There were so many questions and directions one could go on those write-ups. Adding details like: "Upon a cold start up," or "over railroad tracks" could save a tremendous amount of time, and likely help get a customer's car fixed right the first time. Most writers I've worked with won't even get out of their chair to look at a customer's car to see a concern first-hand, or even get the correct mileage.
Sponsored