Extend socket timeout for REST custom flow designer action

[Oleg Grecic]

Hi, 

I'm integrating ServiceNow with Sonatype Nexus repository and when trying to get a full list of users via custom REST Flow designer action, I receive an error Operation(flow_action_name) failed with error: com.snc.process_flow.exception.OpException: Socket timeout. 

I tried the following:

-extending the timeout on HTTP Connection.

-glide.http.outbound.max_timeout and glide.http.outbound.max_timeout.enabled properties did not exist on the instance, I've created them and set the necessary values.

-glide.http.timeout as well does not exist in my instance. 

Please help to bypass this. Yes, the GET request is long, lasts about 2 minutes, but I need it to run daily with no faults. 

[The Machine]

Sounds like it needs to be broken down into more than one call in order to get the full list. Perhaps try breaking it down and use pagination, it’s more work but it’s better than changing some of these default props. 

[Oleg Grecic]

The case is, that there are only 600 records, and the query cannot be cut in some pieces, once sent, it should be fully loaded and only then we can break it down. I tried paginating but no luck, it still goes into "Socket Timeout".

[The Machine]

Something doesn't seem right if its only 600 records.  That should be returning in seconds.  If you make the same rest call in something like Postman, does it still take longer than 2 minutes to retrieve that data?  If it does to take longer than 2 minutes, I'd talk to the person that created the API.

If it returns in a shorter time, it could indicate something is misconfigured with the REST configuration in ServiceNow.  

As far as other options.  Are there other APIs for that system you can leverage and possibly chain together.  For example, an API to get a simple list of the data you need to look up / do something with, and then another API call that gets that individual simple list item details.  Does that make sense?

[Oleg Grecic · Accepted solution]

Resolved the case. For some reason pagination did not work as well for the Sonatype Nexus repository users request. The response time is same as long when trying to query with postman, or simply from browser. I've found a KB that says that this property has to be set within mid-server, so it's not the case that flow designer itself limits the query for 175 seconds, but the Mid Server itself. Link to the KB is here.

In any case thank you for involvement!