AI Agents in Retool

[kent]

@bobthebear

Obviously the select workflow should be changed to select the newly created workflow id, but ignoring that does this recursive call create a whole new external REST request to the workflow or is the backend able to shortcut this sending to http://localhost:xx (or even better, restructure/wrap the workflow in a loop). I'm mostly wondering about the resource usage on the call stack since recursive calls within JS and Python have limits and in the case of JS it depends on the browser. I'm wondering how easily the extra overhead of a recursive REST request could cause a call stack overflow.... you could stick the whole workflow itself into a multi-step function and wrap it in a loop block to avoid the recursiveness, so I guess I'm just curious about the design choice

Short answer is that the backend shortcuts it when the Workflow is called from another Workflow! I wouldn't worry about the call stack - Workflows are orchestrated with Temporal, so there's essentially a queueing system built in that should handle the load. Also just wanted to confirm that these Workflows aren't running on the client, so there shouldn't be anything to worry about from the browser perspective.

You definitely could stick the whole workflow in a loop block (or in a JS loop) and accomplish the same thing - that would work fine too, this was just the method that I chose here.

Indeed - my saveState subflow could have been handled by a single block. There is no reason that it needs to be this case, it was just that while building this, I was preemptively encapsulating that functionality because I assumed I'd need multi-step logic there.