[{"data":1,"prerenderedAt":48},["ShallowReactive",2],{"update-updates_en-2026-10-07-etapas-por-servicio":3},{"id":4,"title":5,"body":6,"date":36,"description":37,"extension":38,"meta":39,"navigation":40,"path":41,"rawbody":42,"seo":43,"stem":44,"tags":45,"__hash__":47},"updates_en\u002Fnovedades\u002F2026-10-07-etapas-por-servicio.md","Stages and versions per service",{"type":7,"value":8,"toc":30},"minimark",[9,14],[10,11,13],"h2",{"id":12},"improvements","Improvements",[15,16,17,21,24,27],"ul",{},[18,19,20],"li",{},"Each service keeps its own stages. The API validates configuration, saves versions and restores a previous version without deleting history. Owners configure; managers read. Tasks continue using the current executor. The visual editor, Wagy proposals and new executor are planned for later changes.",[18,22,23],{},"Migration preserves inactive stages and actions sharing a destination without duplicating buttons. History retains the source blueprint version when configuration is saved or restored.",[18,25,26],{},"Confirmations retain their title and body in all three languages. The API accepts up to 42 stages to preserve existing identities and system canonical stages. Isolated canonical stages add no actions or permissions; configured exits retain graph validation. Validation, saving and restoring accept these migrated configurations.",[18,28,29],{},"Forms and effects that converge on a stage are preserved in full during migration: up to 1024 scalar fields and 512 effects per stage, with a total configuration limit of 256 KiB. Validation, saving without changes and reverting accept these unions. Release from a confirmed stage counts as a path to pending and expiry when validating the graph, without adding exits or permissions. The new executor and uniform effect execution remain pending.",{"title":31,"searchDepth":32,"depth":33,"links":34},"",2,3,[35],{"id":12,"depth":32,"text":13},"2026-10-07","Each service has independent configuration, validation and history.","md",{},true,"\u002Fnovedades\u002F2026-10-07-etapas-por-servicio","---\ndate: \"2026-10-07\"\ntitle: \"Stages and versions per service\"\ndescription: \"Each service has independent configuration, validation and history.\"\ntags: [improved]\n---\n\n## Improvements\n\n- Each service keeps its own stages. The API validates configuration, saves versions and restores a previous version without deleting history. Owners configure; managers read. Tasks continue using the current executor. The visual editor, Wagy proposals and new executor are planned for later changes.\n\n- Migration preserves inactive stages and actions sharing a destination without duplicating buttons. History retains the source blueprint version when configuration is saved or restored.\n\n- Confirmations retain their title and body in all three languages. The API accepts up to 42 stages to preserve existing identities and system canonical stages. Isolated canonical stages add no actions or permissions; configured exits retain graph validation. Validation, saving and restoring accept these migrated configurations.\n\n- Forms and effects that converge on a stage are preserved in full during migration: up to 1024 scalar fields and 512 effects per stage, with a total configuration limit of 256 KiB. Validation, saving without changes and reverting accept these unions. Release from a confirmed stage counts as a path to pending and expiry when validating the graph, without adding exits or permissions. The new executor and uniform effect execution remain pending.\n",{"title":5,"description":37},"novedades\u002F2026-10-07-etapas-por-servicio",[46],"improved","v4bcT8iKMN9HRzL98sMxMYw_9VRKmiHHaIefXkGdd5o",1791458106337]