I have not seen this happen before. However if I had to guess it seems like that the initial estimate for the amount of data to be imported might be inaccurate vs the actual data being imported. However I have not seen any other reports of this specific problem before. So I am curious to learn more about your instance and see if there is a specific problem with our migration process or perhaps if there is something special about your dataset being imported that might be a factor here.
Any other details you can provide here would be helpful as well. Do you have an existing support ticket on our https://getsupport.atlassian.com tracker for this issue?
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.