Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Progress Messages Confusing - Migration Complete, Migration Not Complete...

Featured Replies

When running a migration, the messages are confusing. At first, it says the migration is complete, but the yellow dot remains yellow, then a follow up message appears, "Migration NOT complete..." along with a delay while (presumably) the migration actually progresses towards completion.

Then, finally, green dot and completion.

The competing messages are confusing. For a future release can these be edited to be more descriptive of the actual state of the migration process?

Bonus coverage would be if the system recorded previous migration start/stop times and gave some educated guesses about time required to complete the process. The time required is quite different for different servers/solutions and the reminder would be helpful to me as I sit and wonder how long I have to wait before worrying.

1347344984_Screenshot2019-02-2411_51_15.png.682ab921b24addb2de2bc37ff98e4220.png

Hey MMHinSEA,

To describe your screenshot, this shows that 0 databases have a completed migration, and there is 1 database where the migration is not complete.  As the files are migrated, the databases will move into the "Migration Complete For Databases" section.

We are working on better reporting of the migration process, and I expect this to be included in a future release.

It will be very hard to anticipate the length of the migration, mainly due to the fact that the migration tool makes the call whether to migrate the databases in "block" mode (really fast) or "record" mode (slower, but still fast).  "Record" mode migration is triggered if there is any field definition changed in a table, and can result in a table taking a lot longer to migrate, relatively.  We could potentially analyze the schema differences between dev and prod and guess at which mode the migration tool will use, but this is not a high priority feature for us now, and would involve a good deal of work to get working correctly.

Thanks,

Joe Martin

  • Author

Hi - thanks for replying.

I do understand there are many high and low priorities as you develop the software and look forward to some clearer formatting and/or language in this window.

The specific issue I screen-shotted above could probably be solved easily with a "(none)" in the space below the "completed" heading.

Any kind of progress indication would be welcome. Even an indication showing if block or record based cloning was being used would be helpful. Another easy change that would provide immediately-useful feedback would be to add in the confirmation email a "Total time to complete" line near the top of the message... the start and end times are there, so that should be a trivial calculation.

Thanks~

 

 

Edited by MMHinSEA

Hey MMHinSEA,

I appreciate your concern.  As part of the improved reporting feature, I will add that we should include a "Total time to complete" portion in the report.

Thanks,

Joe Martin

  • Author

Thanks Joe - appreciate it

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.