I can't really see how you managed this, since a script only repeats when the version number wasn't updated in the last step. If you got the message with the link, then the version was correct, so it really should have gone to the link in the first place...
I suppose it's possible if there was a lot of database traffic at the time, and the insert to the upgrade log was delayed until after you clicked proceed, but this would only occur the first time and the second time (or whenever database writes stopped hanging) would display the message or continue to the correct location. Database table locks usually don't work this way (locking the whole database against writes), but I believe that it might occur if you were attempting the upgrade while an automated backup was occurring.
Unfortunately I don't have a version this old installed to see for sure, but all the usual errors in the code for this issue historically are not present.