App developed with OD 7.0.1 , in the flow there is a DB operation where the DB timeout parameter is set to 60 sec for transaction timeout.

When the call flow is interpreted on IVR we see that it is waiting for 60 secs and then throwing a error.badfetch on platform.
The Platform timeout is 15 secs.

Customer would like to know why the MPP timeout is not being considered. As we know the platform timeout for a page will be overridden by the app, would like to know if there is any default timeout that comes into picture for the app during the DB transaction.

From the app trace we see the DB transaction failing after 60 sec timeout:
Line 204757: 27/03/2018 16:03:41:819 INFO - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : [expression4] Expression [AppVariables:TransferCount] Is Null [null]
Line 204758: 27/03/2018 16:03:41:819 INFO - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : [expression5] Expression [AppVariables:TransferCount] Is Empty
Line 204759: 27/03/2018 16:03:41:819 INFO - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Using SCESession 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 servlet : CheckAndGetCustSegment
Line 204759: 27/03/2018 16:03:41:819 INFO - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Using SCESession 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 servlet : CheckAndGetCustSegment
Line 204760: 27/03/2018 16:03:41:819 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Customer Segment (CUSTCAT) Value =
Line 204761: 27/03/2018 16:03:41:819 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : CUSTCAT is EMPTY - Getting Customer Segment (CUSTCAT) For = 067144149
Line 204762: 27/03/2018 16:03:41:819 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - SessionID = 8df371c3-301f-4172-ac8f-da07ff9b4afa
Line 204763: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - TransactionID = 180327160341819
Line 204764: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - ApplicationID = IVR101
Line 204765: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - ChannelID = IVR-101
Line 204766: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - SubChannelID = 101
Line 204767: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - VasCode = DBA
Line 204768: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - ActionID = 001
Line 204769: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - MSISDN = 067144149
Line 204770: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Request To Adapter - AdditionalInfo = {OriginApp=}
Line 204771: 27/03/2018 16:03:41:820 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Sending Request To Adapter
Line 204772: 27/03/2018 16:04:41:942 INFO - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Using SCESession 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 servlet : error_badfetch
Line 204772: 27/03/2018 16:04:41:942 INFO - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Using SCESession 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 servlet : error_badfetch
Line 204773: 27/03/2018 16:04:41:944 DEBUG - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : session id:au1502-2018086120337-14 | IVR101:error_badfetch | ***badfetch***
Line 204774: 27/03/2018 16:04:41:944 INFO - 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 : Using SCESession 65652F4AB1BA727A7AA7B40D23E9827F:/IVR101 servlet : checkNextNode


From the platform we see it is waiting for 60 sec and then throwing error:
@2018-03-27 05:03:41,783||FINEST|CommonVXI.Cache|21314|Session=au1502-2018086120337-14|SBinetChannel::getHttpConnection Called url=https://10.51.169.15:7443/IVR101/error_runtime?___DDSESSIONID=65652F4AB1BA727A7AA7B40D23E9827F%3A%2FIVR101|au1502.etisalat.corp.ae####
@2018-03-27 05:04:41,837||FINE|CommonVXI.Cache|21314|Session=au1502-2018086120337-14|SBinetHttpStream.cpp:1403:SBinetHttpStream::getHeaderInfo: Waited 60053ms for HTTP response|au1502.etisalat.corp.ae####
@2018-03-27 05:04:41,837||FINE|CommonVXI.Cache|21314|Session=au1502-2018086120337-14|SBinetHttpStream.cpp:1409:SBinetHttpStream::getHeaderInfo: rc=51, HttpStatus=-1234|au1502.etisalat.corp.ae####

Whereas the timeout for the below page is 10 seconds.

@2018-03-27 05:04:45,084||FINEST|CommonVXI.Cache|21314|Session=au1502-2018086120337-14|SBinetChannel::getHttpConnection Called url=https://10.51.169.15:7443/IVR101/SendingAICDataOnDisc?___DDSESSIONID=65652F4AB1BA727A7AA7B40D23E9827F%3A%2FIVR101|au1502.etisalat.corp.ae####
@2018-03-27 05:04:55,087||FINE|CommonVXI.Cache|21314|Session=au1502-2018086120337-14|SBinetHttpStream.cpp:1403:SBinetHttpStream::getHeaderInfo: Waited 10005ms for HTTP response|au1502.etisalat.corp.ae####
@2018-03-27 05:04:55,087||FINE|CommonVXI.Cache|21314|Session=au1502-2018086120337-14|SBinetHttpStream.cpp:1409:SBinetHttpStream::getHeaderInfo: rc=51, HttpStatus=-1234|au1502.etisalat.corp.ae####


Let me know if there will be timeout set from app side , I will also have it reviewed from Platform side.

I have attached the app trace for reference. Let me know if you need any other information.

Thanks in advance.

if you need to override the platform fetch timeout, you would have to use the Property item from the palette of a form node (i.e. Announce). The Property item would allow you to set the app level fetch timeout to correspond to the delay you expect for the data operation.