In my experience the update from 3.0.x directly to 3.2.x times out on some setups, sometimes even silently (it does succeed without problems on other configurations but since something went wrong on your side I wouldn't take any risks).
If your database exceeds ± 300MB, just a case I would go for an upgrade in steps, and on localhost (that usually reduces the risk of timeouts)
first 3.0.11 > 3.0.14
second 3.0.14> 3.1.latest (9 I think)
third 3.1. latest >3.2.x
Always keep backups of the intermediate results!!!
It's imperative that your 3.0.x is cleaned before upgrading: in other words: undo all modifications (database modifications), have prosilver and UK English language as only and default style and language.
A bug is a feature that hasn't made it to the manual (yet)