We confirmed this loop problem. The problem is that OPEN is not correctly exectuted in the 2nd, 3rd etc run.
As workaround, we suggest to use the TIMES command instead of the LOOP button. It is usually the more elegant solution anyway.
Video of the issue:
TIMES is intermittent. sometimes it runs perfectly for many rounds. sometimes it just get stuck for no reason or failed after a few runs.
LOOP has never had this issue. Hope LOOP can be resolved soon.
Do you have any tips how to make TIMES work with Csvread as LOOP did? Reading next csv line each loop?
Same error for me…
Is it possible to downgrade ?
If it’s not possible, do you have a solution to use csvread with times ?
Thanks in advance
This issue is solved with today’s V6.3.2 update. Happy New Year!
When I Run a LOOP, that contains the line XTYPE command, to close a TAB on Chrome (Command: Xtype | Target: ${KEY_CTRL+KEY_W}), after some loops I will get the following error:
[error][ignored] Line 17: XClick/XClickText/XClickTextRelative/XMoveText/XMoveTextRelative/XMove/XType 25 commands limit reached
It’s not a bug with the free plan you can use a maximum of 25 Xclick/Xtype/Xmove commands per macro execution and the loop does not reset the count so it’s normal to continue using the X commands you have to buy a license
ok, thanks for your help.