I do not think so... what I did (which is probably NOT a good practice) was to do a backup first (you need it anyway for the migration), delete it (it did allow me to delete even if I had a worker using it) - like you I wanted to use the same name, went through the beta migration, updated the toml binding and used the new ID and then redployed the worker. In my case, it was OK to have an outage
I spoke to soon. I can see the DB, but when I try to query a row: { "result": [], "success": false, "errors": [ { "code": 7500, "message": "internal error" } ], "messages": [] }