You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the front end subscribes to all graph execution events and does aggregation to derive an execution status. We are now going to use this status in more places, so we should do the aggregation in the back end. The aggregation logic also needs updating because of some new added factors that contribute to the overall "agent status".
Requirements
Emits agent execution updates in real time
Part of WebSockets API
The same info needs to be available through the GET /graphs/{graph_id}/runs REST endpoint
Events:
New agent run
Agent run status updated
Queued (can this be combined with "New agent run"?)
Running
Completed
Stopped
Failed
New agent output item
New error (or is this the same as "Failed"?)
The text was updated successfully, but these errors were encountered:
Currently, the front end subscribes to all graph execution events and does aggregation to derive an execution status. We are now going to use this status in more places, so we should do the aggregation in the back end. The aggregation logic also needs updating because of some new added factors that contribute to the overall "agent status".
Requirements
GET /graphs/{graph_id}/runs
REST endpointThe text was updated successfully, but these errors were encountered: