-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zombied parse.com migration, manual migration option #201
Comments
@nncary We have the same problem :-( |
Hi @nncary and @pungme can you please visit https://parse.com/help and find the bug icon / "Something wrong?" section to start the bug reporting flow. As were tuning the migration workflow, it's much easier for us to track those issues individually. We'll need your app id and if you can find it, your migration job id (only new versions of the UI have this). Closing as we prefer to track migration issues through the developer bug tool. |
My parse.com migration job is permanently stuck, where the migration page says its cancelled, but when I go to initiate a new job it says the old one is still running. Is there a way we can run this locally for those of us who just want to make sure we properly capture the schema.
The text was updated successfully, but these errors were encountered: