https://connect.hyland.com/t5/alfresco-forum/best-practice-for-reopening-or-cloning-a-completed-workflow/m-p/492109#M40342 <P>I’m looking for a way to reopen a completed workflow in Alfresco, or at least create a new workflow based on a closed one while maintaining a link/relationship between them.</P><P>This would be useful for simple recurring tasks or situations where a process needs to be restarted with reference to its previous instance.</P><P>Has anyone dealt with this requirement before? Is there a best practice for handling it? Should workflows be designed never to fully complete in such cases, or is there a way to “reopen” them at the database level (or via API) without breaking the integrity of the system?</P><P>Any advice, patterns, or examples would be greatly appreciated.</P> Wed, 13 Aug 2025 22:33:07 GMT la 2025-08-13T22:33:07Z https://connect.hyland.com/t5/alfresco-forum/best-practice-for-reopening-or-cloning-a-completed-workflow/m-p/492109#M40342 <P>I’m looking for a way to reopen a completed workflow in Alfresco, or at least create a new workflow based on a closed one while maintaining a link/relationship between them.</P><P>This would be useful for simple recurring tasks or situations where a process needs to be restarted with reference to its previous instance.</P><P>Has anyone dealt with this requirement before? Is there a best practice for handling it? Should workflows be designed never to fully complete in such cases, or is there a way to “reopen” them at the database level (or via API) without breaking the integrity of the system?</P><P>Any advice, patterns, or examples would be greatly appreciated.</P> Wed, 13 Aug 2025 22:33:07 GMT https://connect.hyland.com/t5/alfresco-forum/best-practice-for-reopening-or-cloning-a-completed-workflow/m-p/492109#M40342 la 2025-08-13T22:33:07Z