Tech Trouble: Restaurant’s Robot Out of Control

A high-tech “helper” at a California hot pot restaurant suddenly turned into a flying-dish hazard—raising a basic question every family understands: who’s responsible when automation goes off the rails in public?

Quick Take

A Haidilao hot pot restaurant robot thrashed during a promotional dance, striking a table and sending dishes and condiments across the dining area.
Reports place the incident in Cupertino (near San Jose), with some coverage using “San Jose” as shorthand for the area.
Three staff members physically restrained the robot; no injuries were reported, but property damage and disruption were clear.
Haidilao representatives said the incident was not a technical malfunction, blaming placement too close to a table at a customer’s request.

What Happened Inside the Haidilao Dining Room

Footage that circulated online in mid-March showed a humanoid, themed service robot performing a routine in a Haidilao hot pot restaurant in Cupertino, California, near San Jose. During the performance, the robot struck a table and scattered chopsticks, dishes, and condiments into the dining area. One employee moved in to intervene but couldn’t stop the machine’s continued flailing, turning a novelty moment into a safety scramble.

Two additional staff members then rushed over and physically restrained the robot while it continued moving erratically. Coverage of the viral clip emphasized that no one appeared to be injured, even as items were knocked loose and cleanup became the immediate priority. The robot’s manufacturer was not identified in the reporting provided, and the video’s virality outpaced any detailed public technical explanation of what precisely triggered the behavior.

Cupertino vs. “San Jose”: Location and the Viral Version of Events

Multiple reports align on the venue—Haidilao hot pot in the South Bay—but differ slightly in how they describe the location. Some outlets use Cupertino, a more precise description, while others say San Jose, likely as a recognizable regional reference for national audiences. The core facts remain consistent across coverage: the robot’s routine went wrong, tableware flew, staff restrained it, and the incident became a shareable symbol of how fast “automation” can become “accident.”

Company Response: “Not a Malfunction,” but a Setup Problem

Haidilao representatives told media that the episode was not caused by a technical malfunction. Instead, the company said the robot had been positioned too close to a table at a customer’s request, restricting safe operation during its routine. That explanation matters because it shifts the debate from “dangerous machine” to “unsafe deployment.” The reporting available does not include a third-party engineering review, leaving the public with competing narratives.

The Real Issue for Families: Liability, Safety, and Basic Control

Even without injuries, the incident highlights a practical concern: customer-facing machines in tight public spaces must have predictable fail-safes and clear human override. Restaurants are dynamic environments with kids, hot surfaces, crowded aisles, and servers carrying sharp or heavy items. When a robot requires three employees to physically tackle it to regain control, that suggests the “human in the loop” remains essential—and that businesses deploying automation should expect scrutiny on training, placement, and emergency procedures.

Automation Hype Meets a Common-Sense Limit

Haidilao has been known for experimenting with automation and customer-facing tech, and the viral incident now serves as a reminder that real-world conditions don’t behave like controlled demos. The available coverage offers limited information on any changes Haidilao made afterward, such as adjusted spacing rules, updated routines, or revised staff protocols. Until companies share more specifics, consumers are left with the video and a simple takeaway: convenience is not a substitute for control.