Operation monitor reload failing with error Timeout when waiting for HTTP response from server

[ArifShah]

Hi,

The operation monitor suddenly started throwing error during relaod

  20200408T132308.018+0200      	19 fields found: userId, userDirectory, __FK_owner, id_u1, __KEY_app, __FK_app, id_u2, engineObjectId, createdDate, modifiedDate, modifiedByUserName, description, objectType, publishTime_u0, published_u0, approved, name_u2, __KEY_root, __extra_, 
      20200408T132308.018+0200      Error: Timeout when waiting for HTTP response from server. Increase the <Timeout> value in your settings.
      20200408T132310.290+0200      Execution Failed
      20200408T132310.440+0200      Execution finished.

Any idea where can I set this time out or how to fix this?

[alex_rosu]

We started experiencing the same issue with the Operations Monitor app. 

2020-09-17 07:02:05 Error: Timeout when waiting for HTTP response from server. Increase the <Timeout> value in your settings.
2020-09-17 07:02:06 Execution Failed
2020-09-17 07:02:06 Execution finished.

Did anyone found any resolution for this issue?

Thanks.

[alex_rosu]

We also get the same error for the Sessions Monitor application.

[vhayward]

Hi,

You can change this in the data connection for the monitoring applications.
These start with the name "monitor_apps_REST_".

The connection string would look like this :

CUSTOM CONNECT TO "provider=QvRestConnector.exe;url=https://ABCDABCDABCDABCDABCDABCD/qrs/app/object/full;timeout=2400;method=GET;

By changing the timeout value from like 900 to 2400 (or something like that ...) you can manipulate the timeout threshold.

Best regards,
Vincent Hayward

[chubb_carlosc]

We've modified the timeout on the string as suggested with 2400, reload task also updated with 2400 timeout, however, the reload tasks keeps failing with the same error.

Error: Timeout when waiting for HTTP response from server. Increase the <Timeout> value in your settings.

any other suggestions that can be modified ?

[André]

I've recently been getting this error too. Happens sporadically and then will just work?