In the demo app, how many records are referenced in the query? In our NPE my query had 62 records which I know isn't much higher than your threshold but these are real records of ours. One work order had over 1000 labor transactions for example, and there was a total of 20 attachments downloaded, so I would imagine it's above and beyond what the demo app contains. And thats with the si.device.connectivity.timeout at 60 seconds. Purely a guess (I don't have a demo app currently available on 7.6.4), but I assume a request is failing instead of a timeout issue.

Out of curiosity, can you try a query that has something like 25 records. The page size for workOrder is 20 records, so if it was something due to pagination I would imagine it error out with 25 records too. As an example, I know the mxe.oslc.webappurl system property has to be adjusted since out of box it points to localhost, causing issues for getting the next page. 

In the demo app, how many records are referenced in the query? In our NPE my query had 62 records which I know isn't much higher than your threshold but these are real records of ours. One work order had over 1000 labor transactions for example, and there was a total of 20 attachments downloaded, so I would imagine it's above and beyond what the demo app contains. And thats with the si.device.connectivity.timeout at 60 seconds. Purely a guess (I don't have a demo app currently available on 7.6.4), but I assume a request is failing instead of a timeout issue.

Out of curiosity, can you try a query that has something like 25 records. The page size for workOrder is 20 records, so if it was something due to pagination I would imagine it error out with 25 records too. As an example, I know the mxe.oslc.webappurl system property has to be adjusted since out of box it points to localhost, causing issues for getting the next page. 

12, 15:58:39.435[ERROR] [ERROR]Unable to load remote page for workOrder, queryBase: getMyAssignedWork, Error: {"invocationResult":{"responseHeaders":{"connection":"close","content-length":"323","content-type":"text/html; charset=iso-8859-1","date":"Tue, 12 May 2020 13:50:07 GMT"}},"errorCode":"UNRESPONSIVE_HOST","error":{"code":414,"message":"Request-URI Too Long","url"​

In the demo app, how many records are referenced in the query? In our NPE my query had 62 records which I know isn't much higher than your threshold but these are real records of ours. One work order had over 1000 labor transactions for example, and there was a total of 20 attachments downloaded, so I would imagine it's above and beyond what the demo app contains. And thats with the si.device.connectivity.timeout at 60 seconds. Purely a guess (I don't have a demo app currently available on 7.6.4), but I assume a request is failing instead of a timeout issue.

Out of curiosity, can you try a query that has something like 25 records. The page size for workOrder is 20 records, so if it was something due to pagination I would imagine it error out with 25 records too. As an example, I know the mxe.oslc.webappurl system property has to be adjusted since out of box it points to localhost, causing issues for getting the next page. 

12, 15:58:39.435[ERROR] [ERROR]Unable to load remote page for workOrder, queryBase: getMyAssignedWork, Error: {"invocationResult":{"responseHeaders":{"connection":"close","content-length":"323","content-type":"text/html; charset=iso-8859-1","date":"Tue, 12 May 2020 13:50:07 GMT"}},"errorCode":"UNRESPONSIVE_HOST","error":{"code":414,"message":"Request-URI Too Long","url"​

In the demo app, how many records are referenced in the query? In our NPE my query had 62 records which I know isn't much higher than your threshold but these are real records of ours. One work order had over 1000 labor transactions for example, and there was a total of 20 attachments downloaded, so I would imagine it's above and beyond what the demo app contains. And thats with the si.device.connectivity.timeout at 60 seconds. Purely a guess (I don't have a demo app currently available on 7.6.4), but I assume a request is failing instead of a timeout issue.

Out of curiosity, can you try a query that has something like 25 records. The page size for workOrder is 20 records, so if it was something due to pagination I would imagine it error out with 25 records too. As an example, I know the mxe.oslc.webappurl system property has to be adjusted since out of box it points to localhost, causing issues for getting the next page. 

12, 15:58:39.435[ERROR] [ERROR]Unable to load remote page for workOrder, queryBase: getMyAssignedWork, Error: {"invocationResult":{"responseHeaders":{"connection":"close","content-length":"323","content-type":"text/html; charset=iso-8859-1","date":"Tue, 12 May 2020 13:50:07 GMT"}},"errorCode":"UNRESPONSIVE_HOST","error":{"code":414,"message":"Request-URI Too Long","url"​

In the demo app, how many records are referenced in the query? In our NPE my query had 62 records which I know isn't much higher than your threshold but these are real records of ours. One work order had over 1000 labor transactions for example, and there was a total of 20 attachments downloaded, so I would imagine it's above and beyond what the demo app contains. And thats with the si.device.connectivity.timeout at 60 seconds. Purely a guess (I don't have a demo app currently available on 7.6.4), but I assume a request is failing instead of a timeout issue.

Out of curiosity, can you try a query that has something like 25 records. The page size for workOrder is 20 records, so if it was something due to pagination I would imagine it error out with 25 records too. As an example, I know the mxe.oslc.webappurl system property has to be adjusted since out of box it points to localhost, causing issues for getting the next page.