I found out that this problem for us, only happened at one stage, and when you did the step manually, there were i think 2 redirects involved, before it was supposed to see som text on the page.
When i added a sleep function to wait for those redirects to take place, this error stopped..
Something has changed in last chromedriver version i guess, that makes it more sensitive to redirects?