bb1000 wrote: ↑Sun Dec 15, 2019 1:50 pm
I have been using the latest version from the Google Extension Store. Not sure what your saying about the ‘!TIMEOUT’ command and if you’re implying that it doesn’t work anymore...because I’ve been using it on my other scripts and they’re working just fine
Your OP in this Thread mentioned:
bb1000 wrote: ↑Wed Dec 11, 2019 3:56 pm
System: macOS 10.14.6 with iMacros free on Google Chrome Version 78.0.3904.108 (Official Build) (64-bit)
... where the iMacros Version is missing...!
... With "iMacros free on Chrome" but this is vague as there are 4 "iMacros free on Chrome" Versions, and yep some "v10.0.5" Version can be seen in your Script, and this is indeed the current/latest Version, but you need to mention clearly that Version in your FCI. That's my Point...
>>>
About '!TIMEOUT', I'm saying that this Command has been deprecated for about 8 years and that you should use the "correct" Command instead (which is '!TIMEOUT_PAGE'), and that you are "nearly lucky" that it still works...
>>>
But hum, OK, just "to be sure", I also went testing in "your" v10.0.5 for CR 'Free' Version, and ah-ah...!, I do notice some different Behaviour indeed, and now I understand your "Issue", ah-ah...!
In my Tests, it looks like the 'SEARCH' Command totally ignores any '!TIMEOUT_xxx' Settings and always behaves like if '!TIMEOUT_STEP' ="0" (or if '!TIMEOUT_PAGE' ="1"). It never waits...! The Check/Search on the Source is only done once, and the Script aborts directly (with '!ERRORIGNORE=NO') or goes further (with '!ERRORIGNORE=YES') while in both Cases (still) displaying the RuntimeError:
RuntimeError: Source does not match to REGEXP='([A-Z0-9]{5}-[A-Z0-9]{5}-[A-Z0-9]{5}-[A-Z0-9]{5}-[A-Z0-9]{5})', line: 5
(Tested on iMacros for CR v10.0.5 'Free', CR76, Win10_x64.)
Hum, OK..., I am not "too surprised", I wouldn't really call it a "Bug", it could be by Design, even if that would indeed be a bit "of a pity" if '!TIMEOUT_xxx' gave some extra Control in v8.8.2, that has been lost in v10.0.5 for CR.
And I will alert @TechSup about it, if they want to have a Look, and "state" about it...
But then, tja, even if that Functionality gets "corrected" in some later Version, which will take a while of course, you would need to live with it, and simply have your Script to loop regularly to check again maybe every 10 Sec for example...
But as you are using the 'Free' Version, you'll only be able to loop your Script Max 100 Times, which would give you about 66 Min of "Autonomy", or make it every 30 Sec to "reach" your original 3 Hours with '!TIMEOUT'/'!TIMEOUT_PAGE' ="100000".
Or consider getting the 'PE' Version, which would allow you to loop your Script indefinitely..., ah-ah...!
As a possible Workaround, you might "think" about trying on FF70/71 with v10.0.2 for FF ('Free'), but I expect you'll probably get the same Behaviour (I didn't test), as v10.0.2 for FF was built on the same Core Core like v10.0.5 for CR.
Another thinkable Workaround would then be to use v8.9.7 for FF (+ FF v55.0.3 or any of the Browsers forked on FF that didn't adopt the WebExtensions Architecture, like PM28, 'Basilisk', 'WaterFox', etc...), but, hum..., nope...! Bad luck, ah-ah...!!
I did some Testing on v8.9.7 for FF + FF v55.0.3 + Win10_x64, and the Results seem to be "even worse" than on v10.0.5 for CR, ah-ah...!
The '!TIMEOUT_xxx' Settings do get "respected" by v8.9.7, => the String is not found (yet), then the Script will "neatly" wait according to the '!TIMEOUT_PAGE/STEP' Setting, but it will then simply hang for ever upon refreshing the Page (manually) from the Browser, oops...! Even after the '!TIMEOUT_STEP' Setting has been finished (I shortened 'TIMEOUT_PAGE' to "=1000" => 100 Sec for '!TIMEOUT_STEP'), the Script still hangs and doesn't move forward anymore...
So here we have a "real Bug", ah-ah...!
I thought it could be related to the fact that I was editing my 'Test Post' in this Thread from PM26, and that that could play a Role, but I also got the same Hanging if I edited that Post directly from FF55 itself also.
So it looks like this 'SEARCH' Command has changed in Behaviour quite a bit over time, from v8.8.2 for FF => v8.9.7 for FF => v10.0.5 for CR.
And the Behaviour that you want, is the one found in v8.8.2 for FF, which is the Version I use myself for most of my "Prod"-Scripts (+ PM v26.3.3), that could be a Workaround for you, but that Version/FCI is getting "pretty old" now (Decb 2019), especially PM26, and I'm very probably the only one on the Forum using that FCI, not too mention that many "fancy"/"modern" Sites don't work "properly" anymore in this Browser...
(But last time I checked (maybe 1 year ago), 'Discord' Servers were still working in it...)
(But I keep using it for some specific Functionality "I need", and that got broken in v8.9.7 for FF from FF52... (About the 'FILTER' Command.))
But maybe without going back to PM26, you also have PM27 that used to work normally with v8.8.7 for FF.
I don't have this FCI myself, so I didn't test, but I would expect v8.8.7 to rather "behave" like "my" v8.8.2 for FF Version, than v8.9.7 for FF...
>>>
So OK, I'll "soft"-alert @TechSup about your Thread, and this "possible" Bug, or at least Change in Behaviour between several Versions, which is not documented, and the Wiki even doesn't mention anything about all '!TIMEOUT_xxx' Settings and how the 'SEARCH' Command is supposed to behave with them... So we already have a (Documentation) "Bug" here anyway...!
- (F)CI(M) = (Full) Config Info (Missing): iMacros + Browser + OS (+ all 3 Versions + 'Free'/'PE'/'Trial').
- FCI not mentioned: I don't even read the Qt...! (or only to catch Spam!)
- Script & URL help a lot for more "educated" Help...