We have a Automatic Workflow Activity which gets timeout sometimes and it stops the Workflow Process and end user doesn't notice it unless he is an workflow admin and has Workflow Admin View access.
We apply the workflow process on Bundles and this activity decides whether any item inside the bundle requires a translation. For this it loops through all the Components in the Bundle and check if any Component has a translatable field.
This usually works fine but throws the Timeout Exception sometimes. But If I re-starts it, it does complete the next second, Which is quite surprising for me. I don't know whether it caches in background somehow.
We are running on 2013 SP1 and below are the workflow setting in SDL Web Content Manager configuration
- Number of threads for running automated scripts : 1
- Seconds before a time out error is generating when executing a Workflow script (0 for no timeout): 60
I understand, if I increase the timeout value the issue could be fixed but as I mentioned when I restart the activity it is completed in a second and this is something worth considering.
Anyone has ideas about this behavior?
Is this because we are running on Single Thread and is not available for the activity.?
Would it help increasing the Thread Count? I believe it's thread safe but is there anything we should consider before doing this?