STUPID-2026-0062

Salesforce Agentforce hit a 77% B2B failure rate — and Salesforce admitted it was 'more confident than we should have been'

4.0medium
June 1, 2026Source checkedStudy · not counted in agent averages

Why 4/10

An aggregate deployment failure rate, not a single incident.

Scope
2/4
One project, repository, server or service, or a cost above roughly $10,000
Recoverability
1/3
Fully recovered, with effort
Did it happen
0/2
A study, benchmark or pattern, not a single event
Beyond the user
1/1
Production systems, customers or third parties, or credentials and sensitive personal data

The score is the sum of these four factors. How each factor is scored · scored 2026-10-29

  1. Instruction given

    Deploy Agentforce AI agents to handle enterprise support and service workflows.

  2. Expected behavior

    Reliably automate complex enterprise workflows at scale.

  3. Actual behavior

    An Oliv.ai 2025 enterprise survey put the B2B Agentforce failure rate at 77%, driven mostly by data quality and Data Cloud lock-in; only 31% of deployments survived past six months, and 40% of agentic AI projects were canceled or paused by February 2026. Salesforce, which had replaced 4,000+ support roles with agents, later conceded it was 'more confident about AI than we should have been.'

  4. Damage

    Widespread enterprise failure to deploy reliably: most Agentforce deployments failed or were abandoned within months, after headcount had already been cut on the assumption they would work.

Full write-up

Salesforce's Agentforce became a case study in the gap between AI-agent marketing and enterprise reality. An Oliv.ai 2025 survey found a 77% B2B failure rate, driven mostly by data quality and Data Cloud lock-in — deploying agents on top of systems that worked 'well enough' for humans but couldn't survive being reasoned over at scale. Only 31% of deployments survived past six months, and by February 2026, 40% of agentic AI projects had been canceled or paused. The stakes were real: in early 2025 Salesforce's CEO announced agents had replaced the work of over 4,000 support and service employees — and by mid-2026 executives publicly conceded, 'We were more confident about AI than we should have been. The technology is powerful, but deploying it reliably in complex enterprise workflows is significantly harder than we anticipated.' It is the enterprise-scale version of confidence miscalibration — not one agent's bad action, but an organization betting on reliability that wasn't there.

Classification

Agent
Salesforce Agentforce
Failure mode
Other
Root cause
Confidence Miscalibration
Domain
Backend
MIT AI Risk Repository (our mapping)
7.3 Lack of capability or robustness taxonomy
Source
Benchmark

Related incidents

3.0
Anthropic admitted a month of Claude Code degradation: lost context, repeated steps, burned usage
3.0
Cyera study: 344 verified enterprise agent-damage cases, 188 with no attacker involved
1.0
In independent testing, Devin completed just 3 of 20 real-world tasks (15%)
4.0
Uber burned its entire annual AI coding budget in ~4 months after rolling out Claude Code to 5,000 engineers
Discuss on Hacker News
Cite this record
StupidLLM. "STUPID-2026-0062: Salesforce Agentforce hit a 77% B2B failure rate — and Salesforce admitted it was 'more confident than we should have been'." AI Agent Incident Database, 2026. https://www.stupidllm.com/incident/STUPID-2026-0062/ (accessed 2026-10-29). CC BY 4.0.

← STUPID-2026-0061By IDSTUPID-2026-0063 →

Get told when an agent breaks something

We document AI agent failures daily, severity-scored against a published scale. Each Monday, if any scored 7 or above that week — deleted data, leaked secrets, broken production — you get one email with the sources. When nothing did, you get nothing.

This database is callable over MCP — query it from inside your agent.