If there is a workflow that can run forever (potentially) with repeated activities, then the history will get filled. Is there a clean way of forking of new clone of the existing workflow (i.e. Flow style) minus the history details (although the relevant aggregated history could be a part of the new clone through input-data)?
First of all, thanks on a awesome library!
If there is a workflow that can run forever (potentially) with repeated activities, then the history will get filled. Is there a clean way of forking of new clone of the existing workflow (i.e. Flow style) minus the history details (although the relevant aggregated history could be a part of the new clone through input-data)?