cancel
Showing results for 
Search instead for 
Did you mean: 

iRPA: error calling a service connecting to SCP service (DOX) and timeout after that.

0 Kudos

Hi,

I've created a bot to consume DOX as an SCP service. Using the Service Key of the SCP service I've build the proper steps to connect to the service, as follows:

The Generate token step is defined this way:

SourceURL: rootData.WS.Input.ServiceKey.tokenURL + '/oauth/token?grant_type=client_credentials'

Input Data: WS.Input.ServiceKey.client

OutputData: sc.localData.token

Data content type: json

Web service call method: get

Is step: (checked)

WS.Input:ServiceKey.client is set in the first step (Set credentials).

When executing the bot, a time out is returned in Generate token. I wasn't able to see anything descriptive in the error, nor in the traces stored in the \log folder of the iRPA Desktop Studio.

I'd appreciate any hint to find the root cause of the error.

Thanks a lot in advance.

0 Kudos

I have also checked several OSS notes regarding the iRPA configuration:

2796986 - Web Browsers Configuration Checks

2799632 - Change Internet Explorer settings to allow IRPA to work

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member717738
Participant
0 Kudos

Hi Francisco Martinez,

As you can see time out occurred after 30 seconds of calling ajax call. Each step has a timeout and usually set to 30 seconds. If the execution of the step exceeds this defined timeout, the callback is raised. It means your get method is taking more than 30 sec. What you can do is, increase the defined timeout limit in sc.onTimeout() or you can use st.disableTimeout() for disabling default timeout handler in that step. Test the ajax call in postman once to know how much time it is taking for get.

Br,

Thousif.

0 Kudos

Hi Mohammad,

Thanks for your response. I've tested the scenario again and now I can see that the ctx.ajax.call error happens right after the execution of the step. The timeout occurs actually a few seconds later. Therefore the error is not a timeout, but the timeout is a consequence of the error. Unfortunately, I cannot see any information in the traces that helps to clarify why the error happens.