#Request time out code

Surprisingly, the code does wait for the function to be fully performed (I get a loading icon), but the response information doesn’t seem to be waiting. It works for one or two records, but beyond that it’ll return a Request Timeout error.

However, I’m having trouble getting a response from the API request that doesn’t timeout. It’s currently functioning, and the other application is able to take the data and perform as required. You might need to increase the number of replicas for the IFS OData Provider as request would hold on to connections for a longer period of time.I’m using the scripting app to send data via API request to another application.Other timeout values like that of the IFS Proxy would need to be increased.Increasing the timeout will increase the load on the system since slow performing operations will consume more time and resources.Look into increasing the performance of the requests or system itself (e.g.rather than doing it online, do it as a background job) Check if there are any alternate ways to do the operation/work which is timing out (e.g.Increasing the timeout values should be considered as a last resort.

For Cloud deployed (IFS Managed) customers this values can be only changed temporarily (upon special request and approval) and would be reverted after the next delivery/installation. Note that this is only applicable for customers using the Remote deployment. Refer Installer Parameters for OData Provider. Changing the Parameter Values ¶Ĭhanging the timeout values needs to be done via installation parameters by updating the ifsappodata parameter values in the custom_values.yaml. I.e:- Request Url, timeout value in the error message.

Increase the parameter values as a short term measure and contact IFS with details of the issue. If so increase the wait preference header value according to above guidelines.Ĭheck if you can optimize the performance of the request.Įx:- Improve the SQL query used in the Quick Report. If you are encountering timeouts use the following steps to figure out the necessary actions to take.ĭetermine whether the timeout in the error message (within brackets) is below than the maximum timeout applicable to the current request (data retrieving/modifying). Message description: 'Operation did not complete in the expected time (10 seconds).' Guideline ¶ When a request timeout is occurred, you will see following kind of an error. In Batch Requests, an individual request (part) is executed with IFS_INTEGRATION_STATEMENT_TIMEOUT timeout independent of its nature (data retrieving/modifying). If it is a data retrieval request then the wait preference must be less than IFS_INTEGRATION_MAX_QUERY_TIMEOUT, if not IFS_INTEGRATION_MAX_QUERY_TIMEOUT is used as the request timeout.įor data modifying request, the wait preference must be less than IFS_INTEGRATION_STATEMENT_TIMEOUT, if not IFS_INTEGRATION_STATEMENT_TIMEOUT is used as the request timeout. (including data persisting ones) (30m by default) IFS_INTEGRATION_STATEMENT_TIMEOUT This is used to define general integration timeout for any given request. IFS_INTEGRATION_MAX_QUERY_TIMEOUT This is used to define max value for integration timeout of data retrieving requests. IFS_INTEGRATION_QUERY_TIMEOUT This is used to define default integration timeout for data retrieving requests. Similar to above, another three parameters are used during request to integration endpoint. In Batch Requests, an individual request (part) is executed with IFS_STATEMENT_TIMEOUT timeout independent of its nature (data retrieving/modifying). If it is a data retrieval request then the wait preference must be less than IFS_MAX_QUERY_TIMEOUT, if not IFS_MAX_QUERY_TIMEOUT is used as the request timeout.įor data modifying request, the wait preference must be less than IFS_STATEMENT_TIMEOUT, it not IFS_STATEMENT_TIMEOUT is used as the request timeout. These parameter values can be overridden for the request using the wait property of HTTP preference header. (including data persisting ones) (15m by default) IFS_STATEMENT_TIMEOUT This is used to define general timeout for any given request. IFS_MAX_QUERY_TIMEOUT This is used to define max value for timeout of data retrieving requests. IFS_QUERY_TIMEOUT This is used to define default timeout for data retrieving requests. Three parameters and a HTTP header is used to implement this concept. In order to improve the server resource utilization and user experience, IFS OData Provider has introduced timeout values related to a request.

Request time out