Complete or abandon the table migration
sharding & workflows
// what it does
cutover finalizes the move: the tables are deleted from the source keyspace and replication stops. reverse-cutover temporarily restores routing if the app breaks right after; cancel abandons the workflow before any cutover.
// shell
$ pscale workflow cutover mydb main 1$ pscale workflow reverse-cutover mydb main 1$ pscale workflow cancel mydb main 1// gotcha
Cutover is the point of no return — only run it after verify-data is clean and the app has run quietly on switched traffic for a comfortable stretch. If the target VSchema has require_explicit_routing_rules, remove it before cutover or it will fail.