Is there any timing on a 5.0.3 release that fixes this issue? It really doesn't make sense for me to continue the migration until this is resolved.