Post #1741459

@zkat @zkat maybe turn it off and on again? specifically, try cancelling the migration from the mastodon side, then start it again