Working with larger Workflows

  • 4 September 2019
  • 2 replies
  • 3 views

Hello,

I have been working on a rather large workflow for a while now. And the Workflow got big enough that the designer starts to behave quite weird, and it's getting progressively harder to work with. Principle problem seems to be in the fact that the WF gets saved VERY often. Such as when I drag a step out to canvas it starts saving , often making it impossible to configure the step before the saving concludes. Which is starting to take a lot of time. Is there maybe a setting or something that would limit the frequency of WF autosaving ? 

Also weird bugs start appearing after a while. Paths and labels showing incorrectly(visual only). I am sometimes unable to use context browser in certain steps until I delete and redrag them back in (Hello more autosaving). Does anybody here have experience working with large workflows and maybe some tips on how to resolve/minimize these issues? 

 

Thank you and have a nice day

Tom


2 replies

Badge +7

Hello Tom-C

 

I hope you are well.

 

This to me seems like a software if not hardware issue. 

-Try getting an update of your K2 environment. below is a link of all the fixpacks you can try to help solve your issue and getting updates.

http://help.k2.com/kb002658

 

https://help.k2.com/kb002104

 

-Make sure you meet the requirements when creating updates. See link below:

 

https://help.k2.com/onlinehelp/k2blackpearl/icg/4.7/default.htm#Plan/Hardware_Reqs_component.htm

 

-Make sure your hardware, mainly your ram, and HD are to able handle the processes. For it seems to me that you are having a processing error, your ram needs to be enough to handles process initiated by your machine.

 

 

 

Hi Tom,


 


Your question regarding the possibility of disabling the auto-save feature for the workflow designer is unfortunately not possible at this time.  However, this has been a widely-requested feature on the K2 feature request forum here:  https://ideas.k2.com/ideas/APIT-I-414.  I would recommend visiting the link, upvoting the idea, and sharing the link with your colleagues to further increase the visibility of this idea to the K2 developers.  I just upvoted the idea myself because I think this would be a great addition to the product.


 


Thanks!

Reply