Process Flow Performance

We had the same issue and what we did was add a new set index.  I am not 100% sure exactly what order we used and I am walking out the door until Tuesday.  If you don't find another answere let me know then and I will talk to my IT person on what index values we used.

Thinking about how to troubleshoot this reminds me of my leaky shower. I want an "instant fix". My plumber knows better, and realizes that you have to go through a systematic process of analysis. In the end, of course, he is right. And after eliminating some of the variables, we indeed locate and fix the problem. The frustrating part is that sometimes it's difficult, if not impossible, to locate the underlying root cause. Sometimes you just have to "make it better". And, of course, it always takes longer than you--and management--want it to take. Since you say the email node takes a while--10 minutes is way to long--it sounds like you know where to start. Does *every* email take a long time? Or just ones that use this flow? Is it just this flow that is slow? A lot of times I find that flows are poorly designed. Have you had "another set of eyes" look at this flow? Sometimes these types of issues are environmental. If every email takes a long time, that would lead me to a network issue. I have also found that there are some underlying settings which can wreak havoc. For instance, the pfserv config settings for trace and logging. Or JVM memory/thread settings in WebSphere. Or OS kernel settings being too low. Just some random thoughts for this morning.