I have a chained activity that takes a bit of time to get from one screen to the

I have a chained activity that takes a bit of time to get from one screen to the next. It's calling a web service, parsing data, and displaying everything in multiple paging grids. I've reduced the time it takes to run from several minutes down to about 30 seconds. The problem is that the form is closing and I have to go to the task list to pick it back up.

I changed the custom.properties timeout setting (conf.suite.REQUEST_TIMEOUT_IN_SEC=60) to 60 seconds, but it still closes after about 20 seconds. Is there another setting that needs to be changed to extend the timeout?...

OriginalPostID-67771

OriginalPostID-67771

  Discussion posts and replies are publicly visible

Parents
  • I'm still looking into this. I triple checked all the activity chaining and everything looks good. I also tried removed all the gateways. Nothing seems to be helping though. I have two script tasks that run multiple instances of themselves. One is in sequence the other in parallel, which both run in parallel by forking the process flow with AND gates on each end. Could executing the scripts multiple times cause an issue? The documentation mentioned something about running multiple chained form instances, but doesn't warn of any issues with multiple chained script nodes.
Reply
  • I'm still looking into this. I triple checked all the activity chaining and everything looks good. I also tried removed all the gateways. Nothing seems to be helping though. I have two script tasks that run multiple instances of themselves. One is in sequence the other in parallel, which both run in parallel by forking the process flow with AND gates on each end. Could executing the scripts multiple times cause an issue? The documentation mentioned something about running multiple chained form instances, but doesn't warn of any issues with multiple chained script nodes.
Children
No Data