[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"update-updates_en-2026-10-06-asignar-tareas-viejas":3},{"id":4,"title":5,"body":6,"date":66,"description":67,"extension":68,"meta":69,"navigation":70,"path":71,"rawbody":72,"seo":73,"stem":74,"tags":75,"__hash__":77},"updates_en\u002Fnovedades\u002F2026-10-06-asignar-tareas-viejas.md","Assigning older tasks no longer fails",{"type":7,"value":8,"toc":59},"minimark",[9,13,18,47,51],[10,11,12],"p",{},"If you changed a service's form (removing fields such as ZIP code, city or neighborhood), open tasks created with the earlier form could not be assigned: you saw \"Check the fields: some data is invalid\". This is fixed for every business and every scheduling mode.",[14,15,17],"h2",{"id":16},"what-changes","What changes",[19,20,21,29,35,41],"ul",{},[22,23,24,28],"li",{},[25,26,27],"strong",{},"Assigning, scheduling, rescheduling, confirming, changing stage and charging"," no longer re-validate data that does not change: a task created with an earlier form keeps working.",[22,30,31,34],{},[25,32,33],{},"\"Previous data\":"," fields the form no longer has stay saved on the task and show read-only in its detail (only shown when there are any).",[22,36,37,40],{},[25,38,39],{},"Editing a task"," validates only the fields of the current form and keeps the previous ones.",[22,42,43,46],{},[25,44,45],{},"When you save a service's form"," we tell you how many open tasks are left with previous data. It is only a notice: it does not block saving.",[14,48,50],{"id":49},"what-does-not-change","What does not change",[19,52,53,56],{},[22,54,55],{},"New tasks and anything a customer or the bot enters are still validated against the current form: an unknown field is still rejected.",[22,57,58],{},"The amount due, the destination and the base price of existing tasks are not modified.",{"title":60,"searchDepth":61,"depth":62,"links":63},"",2,3,[64,65],{"id":16,"depth":61,"text":17},{"id":49,"depth":61,"text":50},"2026-10-06","Changing a service's form no longer blocks its open tasks: they can be assigned, scheduled and charged, and their previous data is kept.","md",{},true,"\u002Fnovedades\u002F2026-10-06-asignar-tareas-viejas","---\ndate: \"2026-10-06\"\ntitle: \"Assigning older tasks no longer fails\"\ndescription: \"Changing a service's form no longer blocks its open tasks: they can be assigned, scheduled and charged, and their previous data is kept.\"\ntags: [improved]\n---\n\nIf you changed a service's form (removing fields such as ZIP code, city or neighborhood), open tasks created with the earlier form could not be assigned: you saw \"Check the fields: some data is invalid\". This is fixed for every business and every scheduling mode.\n\n## What changes\n\n- **Assigning, scheduling, rescheduling, confirming, changing stage and charging** no longer re-validate data that does not change: a task created with an earlier form keeps working.\n- **\"Previous data\":** fields the form no longer has stay saved on the task and show read-only in its detail (only shown when there are any).\n- **Editing a task** validates only the fields of the current form and keeps the previous ones.\n- **When you save a service's form** we tell you how many open tasks are left with previous data. It is only a notice: it does not block saving.\n\n## What does not change\n\n- New tasks and anything a customer or the bot enters are still validated against the current form: an unknown field is still rejected.\n- The amount due, the destination and the base price of existing tasks are not modified.\n",{"title":5,"description":67},"novedades\u002F2026-10-06-asignar-tareas-viejas",[76],"improved","GuAkAKrMqSFLIs9-38xz7vOuxZ85Sz83SvsIEiyCxtU",1791290876236]