Please do share the actual timeout error. Also, you can create Application connection in Workflow Manager:- Connections > Application > New > Web Services Consumer Please set timeout to 240 and assign this connection to web services consumer transformation. Timeout Number of seconds the Integration Service waits for a connection to the web service provider before it closes the connection and fails the session. Also, the number of seconds the Integration Service waits for a SOAP response after sending a SOAP request before it fails the session. Default is 60 seconds.
In general records are read from any source in batches; any session can only handle a certain amount of data at any one time (depending on the structure of the mapping and memory settings), so it's quite common for the source to have to pause reading while some space is cleared up downstream. However, you can consider the records to be processed sequentially; this is important for a lot of the things we do in expression transformations, for example comparing one record to the previous one.
To capture the input and output of a WSC transformation, unfortunately the only option (at least as of 10.2) is to set Verbose Data tracing on for the entire session (Override tracing on the Config Object tab). Setting Verbose Data tracing just on the WSC transformation itself does not log the SOAP request or response.
As Sacha point out only the session log can provide such information. If it is occuring at times, you can write a simple script to check the session log and send the which record was failed to process to concern team.
# Environmental variables initialization
cd $logfile_dir -- Session logfile_dir set in variables
filename=$(ls -t $file_name* | head -1) -- file_name set in variables
while read line;
if [[ $line == *[TRACE] SOAP Request:* ]]
invoice=$(echo $line | cut -d'<tns:Invoice>' -f 2 | cut -d'</tns:Invoice>' -f 1 )
elif [[ $line == *HTTP/1.1 504 Gateway Time-out* ]]
mail -s "wfname: failure due to Gateway Time-out" DLEmailbox << 'Your message along with the invoice variable set above'
Thank you Syed for taking sometime to answer this. I checked your suggestion and the connection is happening when the call is made WebService application where it is getting delayed to get the information and eventually failing the informatica workflow. So we are trying to get the particular record which is causing this to timeout so that we can do a manual processing on the record. Below is the error for your reference. However, I was able to get that specific record by setting the session level Override tracing to Verbose Data
Thanks Sacha for your response on this. I exactly tried this and we may need to set the Session level Override tracing to Verbose Data to log all the records that are being processed. So the last SOAP Request that was being made to the Web Service is the record which is causing the issue.
Thanks Akilan. This helps in retrieving the specific error record and sending it through a mail. Will try this option.