PowerSwitch 10 -> Assamble Jobs -> Bottleneck?
Posted: Thu Aug 22, 2013 3:20 pm
Hello community,
were using PowerSwitch 10 with some existing Workflows that have been working since Switch 8. The Flows weren't changed but somehow i am noticing serious performance issues since whe updated PowerSwitch from version 9 to 10.
One thing i noticed is that in a lot of Flows the "bottleneck" seems to be the "Assemble Job" function, where files keep stacking up in the folder before the "Assemble Job" action. In most flows the "Assemble Job" action simply combines two PDF files, that where separated by the "Dismantle Job" action somewhere earlier in the flow. Its like these files make their way throught the whole flow in some seconds and then keep gathering in the folder right before the "Assemble Job" action and it sometimes takes the action like two minutes to assemble two files, which are there to proceed.
I'm almost sure, that i did not see this behaviour in PowerSwitch 9 with the exact same flows. But don't pin me down to that...
What might i be doing wrong? Where can i maybe check, what the action is "waiting for"? I know the action has rather mighty options to configure or it maybe has changed in functionality between v9 and v10?
Any suggestions would be welcome.
were using PowerSwitch 10 with some existing Workflows that have been working since Switch 8. The Flows weren't changed but somehow i am noticing serious performance issues since whe updated PowerSwitch from version 9 to 10.
One thing i noticed is that in a lot of Flows the "bottleneck" seems to be the "Assemble Job" function, where files keep stacking up in the folder before the "Assemble Job" action. In most flows the "Assemble Job" action simply combines two PDF files, that where separated by the "Dismantle Job" action somewhere earlier in the flow. Its like these files make their way throught the whole flow in some seconds and then keep gathering in the folder right before the "Assemble Job" action and it sometimes takes the action like two minutes to assemble two files, which are there to proceed.
I'm almost sure, that i did not see this behaviour in PowerSwitch 9 with the exact same flows. But don't pin me down to that...
What might i be doing wrong? Where can i maybe check, what the action is "waiting for"? I know the action has rather mighty options to configure or it maybe has changed in functionality between v9 and v10?
Any suggestions would be welcome.