Describe the bug
Workflows successfully create and execute on the backend relay, but they cannot be deleted. Attempting to delete a workflow confirms the action visually or programmatically, but the workflow remains active, continues to trigger, and still populates the dashboard list upon UI refresh.
Steps to reproduce
- Go to the Workflows panel.
- Click on Create New Workflow and configure a basic trigger.
- Observe that the workflow successfully triggers and runs on the backend.
- Click on the Delete button next to the newly created workflow (or run
buzz workflows delete <id> via CLI).
- Refresh the page or restart the client and see that the workflow has resurrected and is still running.
Expected behavior
The workflow should be permanently deleted from the database and relay, immediately halting all future trigger executions and removing the entry from the UI list.
Version and platform
- Buzz version: [e.g., 0.1.0-alpha - check your Settings sidebar]
- OS: [e.g., Windows 11, macOS Sequoia, Ubuntu 24.04]
Logs / additional context
The terminal/relay logs show an accepted deletion status event, but the tracking database fails to clear the event record, causing the workflow definition to persist.
Temporary workaround used: Manually setting enabled: false via configuration updates to force the backend engine to ignore the triggers.
Describe the bug
Workflows successfully create and execute on the backend relay, but they cannot be deleted. Attempting to delete a workflow confirms the action visually or programmatically, but the workflow remains active, continues to trigger, and still populates the dashboard list upon UI refresh.
Steps to reproduce
buzz workflows delete <id>via CLI).Expected behavior
The workflow should be permanently deleted from the database and relay, immediately halting all future trigger executions and removing the entry from the UI list.
Version and platform
Logs / additional context
The terminal/relay logs show an accepted deletion status event, but the tracking database fails to clear the event record, causing the workflow definition to persist.
Temporary workaround used: Manually setting
enabled: falsevia configuration updates to force the backend engine to ignore the triggers.