While upgrading Workflow Server from 8.3 to 9.1.1, some of the workflows running were stuck at 'SDK Script'. Is this an expected behaviour and if yes then what is the solution to this?
Do you have multiple workflows with the script activity running simultaneously? I have this problem when running script activities in workflows that can run in parallel and always find a way to ensure they run one at a time. You can use a schedule and for each loop as a work around.
Hi Chad,
Yes I actually do. We had two workflows with SDK script activity, and them both runs at the same time, where the output of first workflow triggers the second. So if there are large number of documents keep coming in, we have both workflows running at the same time (but ofcourse at different entries).
Thanks
This definitely isn't intended behavior. Do the workflows end on the script step, or are they in a constant running state?
Hi Zachary,
We have experienced this behaviour many times.
First, we had workflows stuck at SDK script activity, while we were at WF 8.3.
We then upgraded to 9.1 to avoid this issue (as suggest by LF support to upgrade to WF first to the latest version), and after successful upgrade, we had some of the workflows stuck at Running/Waiting stages at the SDK script.
Was there a resolve to this issue?
We are experiencing the same issue.
Workflow is running/waiting on the SDK.
Hi Mason,
I didn't actually.
As a workaround, I created a new workflow using pattern matchings and paddings, as this fulfils my requirements and replaced SDK scripts.
The scripts are throttled on the server for overall performance reasons. As such, it is possible that slower scripts (from other workflows) that take longer to run are causing your script in the current workflow to get queued up. You may be able to see the currently running ones under Advanced Diagnostics\All Tasks in the Workflow Administration Console.
Do you have any scripts executing long running operations like OCR, or launching other executables?
Note that there isn't a lot of information to go on in your post and this is just a guess based on the default configuration and expected behavior of a Workflow Server. For proper investigation of the issue, you should contact Tech Support.