Hello,
I was wondering if I can find out more info about some E_TIMEOUT errors, I get with some tasks.
The tabs are loaded in live tabs in the browser, they are fully loaded and even when I click into the tab until it closes, it still shows the error. And I have no idea why it thinks so.
Is there some additional log?
Thank you!
the most common reason is page not loading. other non-common reason could be scripts failing to load in the page within the timeout period.
what have you observed about the cases where it doesn’t make sense? for example, do they work if you use a different device, say the desktop app or a different browser?
generation information about the error is discussed here: https://distill.io/docs/web-monitor/troubleshooting-errors/#e_timeout
Hi Ajit,
It’s the same with the App, just, that I don’t see the loading page there.
The issue in Chrome is also, that the page is loading fully fine in the tab, that opens for the check. There seems to be nothing missing. The timeout is set in config to
“timeout”: 720,
“delay”: 360
, which should be enough time for everything by far. The pages also load and close just fine, when I have that tab on focus.
I have read that wiki article and nothing helped, so far.
So I’m puzzled about what is going on.
does it happen for all pages you are monitoring or only for some?
setting these is not recommended unless you really know what you are doing.
It only happen with around 15% of them.
for these 15% that error out, do they always error out with a timeout error or are then intermittent?
They stay in E_TIMEOUT always.
I noticed, that sometimes, while the tab still loads, the status goes to timeout already. Despite 30 second delay in the settings and the tab still loading. It loads around 3 seconds max, but Distill is already finished and decided on it being a timeout. The tab closes later even.
But the normal behavior is, that they open, wait their time and then go into timeout.
There is one, that is even NA, never had a successful run. Another was NA till some hours ago, when it somehow worked.
The strange thing is, there is also one check, that worked just fine for years, but stays in Timeout now. I don’t think I changed something there, or maybe I did change the sound, since it used a custom sound in another device and that sound file was N/A in the new device, so no sound played. But it worked before. But not now. I don’t know, if it is related.
Currently there are 10 of these. And they stay like that. Others run and work, they don’t.
can you share 3 of these urls that have always errored out and displaying “NA”? i will test them out and let you know what i find out. thanks!
I only have one such task: Braintrust | Transforming Hiring with AI Recruiting
The config json is pretty much standard:
{
“ignoreEmptyText”: true,
“includeStyle”: false,
“dataAttr”: “text”,
“selections”: [
{
“frames”: [
{
“index”: 0,
“excludes”: [
{
“type”: “css”,
“expr”: “[class*=‘jobs-container_container’] div [class*=‘section’] .styles_wrapper__bJGAo”
}
],
“includes”: [
{
“type”: “css”,
“expr”: “[class*=‘jobs-container_container’]”,
“fields”: [
{
“name”: “text”,
“type”: “builtin”
}
]
}
]
}
],
“dynamic”: true,
“delay”: 30
}
],
“incognito”: false,
“regexp”: {
“expr”: “”,
“flags”: “gim”
},
“blockAdsAndCookies”: true
}
These timeout issues were rare, when I had less tasks. Now I have 50 and it is around a fifth of all tasks.
But it happens, even when only one of these error tasks get checked. So it’s not overworked or something.
I just disabled checking for the app, then marked all 10 tasks to check and enabled the check in the app again. It loaded 5 tabs, which is the setting I gave the device, then after some seconds, it changed all the statuses from checking to waiting. After half a minute, it closed the tab and the timeout error appeared.
It seems to me, it decides too early, that it is a timeout. And does so in bulk. It ran through the 10 tasks pretty quick. Even though the tabs fully loaded.