For what it's worth, the solution that I just used was to set the priority manually on the database, with something like `UPDATE required_action_provider SET priority = 10;` . That appears to have worked around this migration bug.