The proxy network speed is too slow, resulting in a long tweet time

[958]

Dear Mr. Martin. The proxy I use has a slow network speed, which always causes the browser homepage to automatically close and reload before it is fully loaded. The TD log shows that the bridge has timed out. I changed the global timeout but it didn't work. How can I set it to make the browser load longer? The network is not working well, and it always closes and reloads automatically halfway through loading, and it will load multiple times. A task will take 20 minutes and fail. I used the change profile task and found that it was faster. It seems that the network will not fail even if it is a little slower. I observed that after the browser opens the homepage, it directly jumps to https://x.com/settings/profile, the link to change the profile. If TD also opens the homepage and jumps to the tweet link https://x.com/compose/post when performing the tweet task, will it be faster? Can the bridge response time be longer? I need a longer loading time. I changed the timeout to 180 seconds in the browser settings, but it didn't work. The log shows

Waited: 15/600s
Waited: 30/600s
Waited: 45/600s
Waited: 60/600s
Waited: 75/600s
Waited: 90/600s
Received result:
success: False
status: 0
ResponseURL:
Issues:
Warnings:

Bridge Error: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:3316118548
ExFailed: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:3316118548
Setting failed log: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:3316118548
FAILED postmedialoop: Failed in row:

[958]

Read result: C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\tdb\app\write\543065249
Waited: 15/600s
Waited: 30/600s
Waited: 45/600s
Waited: 60/600s
Waited: 75/600s
Waited: 90/600s
Received result:
success: False
status: 0
ResponseURL:
Issues:
Warnings:

Bridge Error: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:543065249
ExFailed: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:543065249
Setting failed log: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:543065249
FAILED postmedialoop: Failed in row: 1/10 23492384629387462387462834 : ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:543065249
Pausing for: 9

[958]

Read result: C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\tdb\app\write\3693531691
Waited: 15/600s
Waited: 30/600s
Waited: 45/600s
Waited: 60/600s
Waited: 75/600s
Waited: 90/600s
Received result:
success: False
status: 0
ResponseURL:
Issues:
Warnings:

Bridge Error: Exception Timeout 20000ms exceeded.
Call log:
- - taking page screenshot
- - waiting for fonts to load... job:3693531691
bridge detection error: timeout
Setting failed log: timeout
FAILED postmedialoop: Failed in row: 6/10 98324823794237542 : timeout
Pausing for: 6

[martin@rootjazz]

Honestly if the proxy is THAT slow, you should get better proxies.

But I can give you an option to increase the timeout for a browser job to complete, default at the moment is 10 minutes. But I Will let you edit that

Bridge Error: Exception Timeout 20000ms exceeded.
Call log:

I'd need full logs as it says here the the timeout is 20 seconds

Bridge Error: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:543065249
ExFailed: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label job:543065249

program tried to click an element and that failed. Why? I don't know. I'd need to see the full logs to know more



But I will be honest, I cannot really dedicate much time to helping you work with such low quality / poor proxies. The solution is better IPs / proxies



Regards,
Martin

[martin@rootjazz]

Next update will include TOOLS > BROWSER > BROWSER JOB TIMEOUT >

This will let the job process longer than the 600s before job read timeout issue stopping the job



Regards,
Martin

[martin@rootjazz]

https://rootjazz.com/twitterdub/updatetesting.html


Tools > Browser > rollback / install > 95




Regards,
Martin

[958]

https://rootjazz.com/twitterdub/updatetesting.html


Tools > Browser > rollback / install > 95




Regards,
Martin

Thanks Martin, I tried it but it still doesn't work. I have updated to the latest version. When the task is running, it loads Google with a blue icon, and it keeps showing a bridge error timeout of more than 20 seconds. If the homepage loads for more than 20 seconds, the browser window will close and reopen. The homepage is not loaded yet and it automatically reloads. I tried many times but still can't upload the log. Can the loading time be set longer? It looks like the homepage did not load within the set time and then reloaded

[958]

Setting bridge start: 2025-03-21 1442
Try write: 0
Success: Write job: C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\tdb\app\read\2742246571
Read result: C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\tdb\app\write\2742246571
Waited: 15/600s
Waited: 30/600s
Waited: 45/600s
Received result:
success: False
status: 0
ResponseURL:
Issues:
Warnings:

Bridge Error: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\logs\e248484b-435e-487d-bcbb-b797ac9e3636.jpg job:2742246571
ExFailed: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\logs\e248484b-435e-487d-bcbb-b797ac9e3636.jpg job:2742246571
Setting failed log: ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\logs\e248484b-435e-487d-bcbb-b797ac9e3636.jpg job:2742246571
FAILED postmedialoop: Failed in row: 8/10 23492384629387462387462834 : ExFailed EX_FAILED: LOG_ID_SCREENSHOT initial click tweetTextarea_0_label C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\logs\e248484b-435e-487d-bcbb-b797ac9e3636.jpg job:2742246571
Pausing for: 5

[958]

The homepage seems to reload after exceeding the timeout period. How can I set the loading time? When the network is not good, the homepage will keep loading before it is fully loaded. If I can set the homepage loading time to 5 minutes, there should be no problem. Can this problem be solved by waiting until the homepage is fully loaded before performing other click operations?

[958]

My computer still cannot submit logs, so the problem I described may be different from your understanding.