An agent that does processing and loops until a count (based on updated environment variable) is reached works fine on V5, but stops after 15 iterations in V6.5.
A simple agent (without the count increments) that shows the problem is as follows - This also stops at 15 iterations.
Agent name = “johnstest”…
Agent Type = Run Once
@prompt([ok];“This should repeat many many times”; “but stops after 15 iterations”)
@command([toolsrunmacro];“johnstest”)
<<<<<<<<<
Is there a “maximum iteration” setting somewhere in V6.5?
Thanks in advance… John
Subject: RE: Old V5 command language agent that called itself now stops after 15 hits
Don’t know, but this is a really kludgy way to do a loop. Can’t you use @For?
Subject: RE: Old V5 command language agent that called itself now stops after 15 hits
totally agree - but this is old V3 code that has been migrated thru (to now V6.5). It should work, and we shouldn’t have to re-write existing code to get it to run in V6.
You’ll recall that in the dim & distant v3 past, recursive agent’s could only be written this way.
I changed toolsrunmacro to RunAgent and that fails after 15 hits with “Too many recursive formula evaluations”.
Smells like a bug to me.
Subject: RE: Old V5 command language agent that called itself now stops after 15 hits
I don’t want to argue with you about whether this is or is not a bug. I’m just suggesting that you be practical about it. The workaround is easy; why do you insist in keeping this obsolete implementation when it’s so easy to make it work correctly and more efficiently?
Subject: RE: Old V5 command language agent that called itself now stops after 15 hits
Andre - if you thought I was being argumentative or intransigent then apologies.
I changed that agent at outset, but my posting was with regard to whether there was a new V6 setting that limits the no. of iterations.
For example, I believe there is a new default of 120 seconds duration for any formula running on the server - I was wondering if there was a simuilar server/client based setting re “Max loops = 15”.
I hope that you appreciate that as the problem arose without any notification/log entry (ie it was only because a “wise” user knew they should have more than 15 results), my major concern is the possibility that there are a lot more legacy systems with such old (and yes, by todays standards, cludgy) approaches that haven’t yet been detected - and an investigation to weed out any (as of yet undetected) failing agent that calls itself via ToolsRunMacro would be a nightmare to perform.
Kind regards … John