Your Agents Are Getting More Capable. Is Your Observability Tooling Keeping Up?

What changed: Salesforce expanded Agentforce Observability with deeper session context, multi-agent traces, an editable LLM-as-judge scoring model, and a rebuilt dashboard — and it’s now included without additional Data Cloud metering for all Agentforce customers.

Why it matters: If you run customer-service or CRM-connected agents, this turns opaque session logs into structured traces you can debug, measure, and score against business definitions — so you can find and fix failing workflows instead of guessing.

Try/watch: Turn on the new session traces for a high-volume agent, export a failing-session sample, and use the editable judge prompt to align the outcome metric (deflection, escalation, or resolution) to your legal or SLA definition; watch token-cost or compliance impacts.

5 Reasons to Upgrade Your Agent to Agent Script

What changed: Salesforce is moving builders to a new Agentforce Builder powered by Agent Script and is freezing development on the legacy builder; Agent Script combines deterministic rules with LLM reasoning (hybrid reasoning), adds built-in debug traces, faster execution paths, and a migration path that deactivates the old agent once the rebuilt one is activated.

Why it matters: For regulated workflows (finance, HR, support) Agent Script lets you enforce business rules deterministically while still using LLMs for reasoning — reducing variance, latency and token costs, and making agents auditable and easier to hand off to non‑developers.

Try/watch: Plan a one‑agent migration: pick a high-value use case with measurable KPIs, rebuild it in the new builder using Agent Script, validate via the debug traces, and measure latency, cost, and error-rate changes before flipping to production.

Microsoft backs ‘agentic’ lab orchestration with Microsoft Discovery and SPARK

What changed: Microsoft announced a $60M package and the SPARK program office to support the DOE’s Genesis Mission and highlighted Microsoft Discovery (now generally available) with features for autonomous lab orchestration, continuous learning, agentic memory, and multi‑hop reasoning over scientific data estates.

Why it matters: This is concrete enterprise signal that agentic AI is moving from chat-and-search to reliable, automated workflows for complex operations — here applied to lab automation and regulated R&D — meaning vendors and buyers should expect more production-grade agent orchestration patterns and governance playbooks for mission‑critical workflows.

Try/watch: If you support scientific, engineering, or regulated operational teams, map where an agent could safely automate repetitive orchestration steps (experiment setup, run, capture results), then pilot with strict guardrails and human checkpoints so you can collect failure modes and governance requirements before scaling.