This shouldn't break existing running schedules because the scheduler manages those all by name, correct?
Unfortunately, we managed all of them by id currently. So this is a hard breaking change. All existing schedules on the crontab will be invalid, and so will all schedule attempts. The user will need to restart all schedules with dagster schedule wipe && dagster schedule up, but it's possible we could write a migration script.
Not sure if the migration script will be worth it.