On what's worth automating: it splits roughly into two camps.
The most common are repetitive operational things — monitoring
markets, responding to messages, deploying code, updating
spreadsheets. But the more interesting use cases are
decision-based: the trading agent deciding when to open/close
positions, or a support agent deciding whether to escalate.
The Event Hub is what makes the decision-based ones viable.
Agents subscribe to real-time events and react based on
triggers — you can use structured filters or even natural
language conditions ("fire when the user seems frustrated").
So the agent isn't just on a cron loop, it's genuinely
reacting to context.
On failure states: agents have built-in timeouts on
subscriptions, automatic retries with exponential backoff,
and silence detection (they can react to the absence of
events, not just their presence). If something breaks, the
subscription expires and the agent can re-evaluate. Long-
running agents also persist their state across restarts so
they pick up where they left off.
There's also a workflow builder where you connect multiple
agents together in non-linear graphs — agents run async
and pass results between each other. So you can have one
agent monitoring, another analyzing, another executing —
all coordinating without a linear chain
The Event Hub is what makes the decision-based ones viable. Agents subscribe to real-time events and react based on triggers — you can use structured filters or even natural language conditions ("fire when the user seems frustrated"). So the agent isn't just on a cron loop, it's genuinely reacting to context.
On failure states: agents have built-in timeouts on subscriptions, automatic retries with exponential backoff, and silence detection (they can react to the absence of events, not just their presence). If something breaks, the subscription expires and the agent can re-evaluate. Long- running agents also persist their state across restarts so they pick up where they left off.
There's also a workflow builder where you connect multiple agents together in non-linear graphs — agents run async and pass results between each other. So you can have one agent monitoring, another analyzing, another executing — all coordinating without a linear chain