Fixed Agent Deletion

Customers reported that deleting an AI agent sometimes appeared to succeed but left behind associated data — knowledge base entries, conversation references, and Slack channel bindings.

Root cause

The deletion logic didn’t account for the correct order of dependent record removal. Foreign key constraints would block the deletion silently, and the UI showed success before the backend confirmed the operation.

The fix

Agent deletion now follows a strict dependency order: Slack channel bindings are cleared first, then conversation references, then knowledge base entries, and finally the agent record itself. The UI waits for backend confirmation before showing the success state.

Clearing Slack settings

As part of this fix, we also added proper cleanup of Slack settings when an agent is removed. Previously, the Slack channel would remain configured even after the associated agent was deleted, causing confusion when setting up a new agent.