The time this task takes to run is so short that using the historial timeout data is not reliable. Sometimes the multiversion setup step can just take a long time to download multiversion binaries and it will exceed the timeout. We could possibly change the historical timeout logic to fix this but this issue is not very widespread so the easier change is to just manually increase the timeout.