Wait Until Page Contains ignores timeout

[axi92]

Version: 1.5.0.4 Appium Version: 1.15.1 We are using the "Wait Until Page Contains" in an loop. The first call is handled in 1s as we specify the timeout. In the second iteration the timeout is still 1s but the command needs 10s to finish. The expected behavior is that the Keyword fails after 1s, instead it fails or passes after 10. The offset in the log is 1h but you can see that the response took Appium about 10s (10199 ms)

2019-11-05 12:11:28:094 [HTTP] --> GET /wd/hub/session/f67af29f-1ea3-4adf-aee3-c1cb5699d088/source
2019-11-05 12:11:28:095 [HTTP] {}
2019-11-05 12:11:28:095 [W3C (f67af29f)] Driver proxy active, passing request on via HTTP proxy
2019-11-05 12:11:28:098 [WD Proxy] Matched '/wd/hub/session/f67af29f-1ea3-4adf-aee3-c1cb5699d088/source' to command name 'getPageSource'
2019-11-05 12:11:28:098 [WD Proxy] Proxying [GET /wd/hub/session/f67af29f-1ea3-4adf-aee3-c1cb5699d088/source] to [GET http://localhost:8200/wd/hub/session/97f50ee8-d708-4cd7-8cdb-5355c1f9f745/source] with body: {}
2019-11-05 12:11:38:292 [WD Proxy] Got response with status 200: {"sessionId":"97f50ee8-d708-4cd7-8cdb-5355c1f9f745","value":"<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>\r\n<hierarchy index=\"0\"...
2019-11-05 12:11:38:293 [WD Proxy] Replacing sessionId 97f50ee8-d708-4cd7-8cdb-5355c1f9f745 with f67af29f-1ea3-4adf-aee3-c1cb5699d088
2019-11-05 12:11:38:294 [HTTP] <-- GET /wd/hub/session/f67af29f-1ea3-4adf-aee3-c1cb5699d088/source 200 10199 ms - 5688

[serhatbolsu]

how do you provide the script sample please?