I have a two-part question about K2 workflows. We're using K2 5.2.
1) We have a workflow we'd like to have fire when a new item is added to a SharePoint list. Then, we would have a timer that waited until its Event Date + 1 day, then it would move the item to an archive list. I'd say an average of about 5 items are added each week, and they are kept for up to a year or so, so there would be an average of around 500 active workflow instances waiting for their next step at any given time. How would having that many active workflow instances affect the performance of our K2 service?
2) We have another workflow that moves any items in the same list that are marked as Rejected to the archive, which is kicked off when the edit form is submitted with a status of Rejected. If the items are marked Rejected and moved to the archive using this secondary workflow, how would that impact the active workflow instance mentioned above? When the event date passed, if they were already in that archive list, would they error out?
Thanks for your insight!
Best answer by Mike_K2View original