@BrettJohnson2
It would be great if you could provide enough details, so this can be reproduced - otherwise I would have absolutely no idea if/when it would be fixed, and you would be stuck on 0.33.x
You are not reverting, you are downgrading. Metabase does not support downgrading. Please revert to a backup.
If you don't have a backup, then it's good time to create a backup now and make sure that you always have backups before doing any major changes (like upgrading, downgrading, etc).
And you would have to manually revert the changes done during the migration. And if you then try upgrading again in the future, then you would have to undo the manual changes you have done.
It's very easy to get the entire application database into a corrupted state, so since you're doing everything manually, then you have to remember those changes.
See this topic for details on what to change: Unknown column 'metabase_field.special_type' in 'field list'