For what is worth, I believe that the reason for this is the following:
- The agent chat component is linked to a query, in this case your agentChat4_query1
- As designed, if you use agentChat4_query1.agentInputs, it would contain the message, and the
invoke
property, like:
-
once it triggers, it will start polling, and the chart action property will change to
getLogs
:
-
It will keep doing it until it gets the results for that agentRunId
-
What is happening with what you're doing, is that the query's data is not changing to
getLogs
. It is actually triggering the query every time because it is trying to poll, but actually is triggeringinvoke
each time
Not sure if there is a way of capturing the promise in a transformer and link that to the action
property in your message setting, so that you can dynamically set whether it is invoke
or getLogs
Hope that makes sense