Docs for key renames: ids and keys in the flow concepts, the rename routes, events and 503s in the API reference, hooks during a rename, sync and run metrics after one; a pinned restore refused for its recorded key names that key in the 409

2026-11-03 08:09:35 +01:00
parent f9d5f510c2
commit b7f1d21712
7 changed files with 75 additions and 9 deletions
@@ -221,7 +221,9 @@ flow reports `unchanged`.
 Sync finds a flow by its declared key. The first sync creates it, and the
 engine gives it an id, which sync prints beside the key. Another engine gives
 the same flow another id, so the key is what your code and every instance
-share. See the
+share. The editor does not rename the key of a synced flow. Changing the key
+in your code makes the next sync create a second flow under the new key, with
+an empty history, and leaves the old one as it is. See the
 [data science guide](../getting-started/data-science.md) for a complete example.

 ### `fluksio run`