Need pagetimeout and continue script...

Support for iMacros. The iMacros software is the unique solution for automating every activity inside a web browser, for data extraction and web testing.
Forum rules
iMacros EOL - Attention!

The renewal maintenance has officially ended for Progress iMacros effective November 20, 2023 and all versions of iMacros are now considered EOL (End-of-Life). The iMacros products will no longer be supported by Progress (aside from customer license issues), and these forums will also no longer be moderated from the Progress side.

Thank you again for your business and support.

Sincerely,
The Progress Team

Before asking a question or reporting an issue:
1. Please review the list of FAQ's.
2. Use the search box (at the top of each forum page) to see if a similar problem or question has already been addressed.
3. Try searching the iMacros Wiki - it contains the complete iMacros reference as well as plenty of samples and tutorials.
4. We can respond much faster to your posts if you include the following information: CLICK HERE FOR IMPORTANT INFORMATION TO INCLUDE IN YOUR POST
Post Reply
super_hiro
Posts: 15
Joined: Tue Feb 23, 2010 2:06 pm

Need pagetimeout and continue script...

Post by super_hiro » Mon Aug 30, 2010 8:45 am

Hi,

I use my macro to list an item to a website automatically.
First, the macro loads the page, then continues with the script.
Problem occurs after I input other datas the page begins to start loading itself again...

I have set in the beginning:

Code: Select all

SET !TIMEOUT 20
SET !TIMEOUT_TAG 5 
SET !ERRORIGNORE YES
But it doesn't help.

After it waits about 20 seconds, the macro just freezes and does not continue on to the next step.
Image

Has anyone got past this error? How do I make the macro continue the script after the timeout?
Tom, Tech Support
Posts: 3834
Joined: Mon May 31, 2010 4:59 pm

Re: Need pagetimeout and continue script...

Post by Tom, Tech Support » Thu Sep 02, 2010 6:26 pm

Hello super_hiro,

Can you please post the URL of the web page and/or the macro that creates the problem? This would allow us to quickly re-create the issue on our test systems.
Regards,

Tom, iMacros Support
Post Reply