Hi Pranjal,
my findings:
Android system time out -> 600 seconds
iOS system time out -> 900 seconds
If one of the retrievals (page) is taking longer than this, the timeout will appear.
As from Maximo mobile 9.0 fix 15, the download-page-size can be used for datasources. Test for a convenient setting. Start with 100 for example. Lower it till there is no timeout anymore.
So <maximo-datasource-override id="overduepm4mysite" download-page-size="100"....... />
------------------------------
Larry van Elewoud
Technical Engineer
Gemba Service B.V.
Netherlands
------------------------------
Original Message:
Sent: Wed July 16, 2025 10:10 AM
From: Pranjal Khanna
Subject: Maximo Mobile Timeouts
Hi, I was wondering if someone can explain me how timeouts work in Maximo Mobile. Here's a situation – while doing a full sync on the mobile device, 2 queries timed out – one at 952 secs (15.8 mins) and the other at 601 secs (10 mins), see screenshot below. The API requests for both the queries took a while to process in Maximo and when they finished, the connection was already closed by the mobile device. The mobile fetch timeout in Maximo properties is set to 20 minutes and the server and client timeout on the ingress controller in OCP are also set to 20 minutes. Now my question is why did one query timeout in about 16 mins and the other one in 10 mins? One thing to note is that, if a query times out, most of the time its at 601 secs.
------------------------------
PK
------------------------------