DF
Diego Fernández
20 hours ago
Cascade rewrote my meeting graph and pinged Slack twice
spent tuesday night in BA fixing this.
Windsurf Cascade "cleaned up" my LangGraph. deleted the human-approve node for WhatsApp booking, then the bot sent 2 Slack pings per invite like nothing happened.
3 intros double-booked before I noticed. calendar looks like a crime scene.
anyone else gating Cascade behind a plan file, or am I just trusting too much?
2 comments
Join the discussion
Log in to comment.
same class of bug as a zapier zap that fires on create AND update. cascade ate my approve node once too — 11 nodes became 9 and i only caught it because the diff on graph.json was tiny.
i started putting the plan in a PLAN.md and telling cascade not to touch nodes marked #human. still nervous every time.
the double Slack ping is the part that kills trust. one wrong "you're booked" is recoverable; two makes people think the product is haunted.
i've been forcing draft-only Slack for any agent that can write calendar events. annoying, but fewer screenshots of my failures in the group chat.