[BUG]Workflow is created and runs, but is missing from the Workflows list on a self-hosted relay
- Dominant language
- Rust
- Stars
- 32.7k
- Forks
- 4.3k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 253
Description
## Summary
A webhook workflow can be created successfully on a self-hosted Buzz relay and runs correctly, but Buzz Desktop continues to show an empty Workflows page (`No workflows yet`).
## Environment
- Buzz Desktop: v0.4.22
- Relay: self-hosted Docker deployment
- Relay URL: custom `wss://…` domain behind Cloudflare Tunnel
- Channel: a newly created channel
## Steps to reproduce
1. Connect Buzz Desktop to a self-hosted relay.
2. Create a channel.
3. Open **Workflows** and create a workflow for that channel:
- Trigger: `webhook`
- Action: `send_message`
- Channel override: the channel’s UUID
4. Save the workflow.
## Actual behavior
- The create flow succeeds and shows a webhook URL plus `X-Webhook-Secret`.
- Calling the webhook successfully posts messages into the selected channel.
- Refreshing the Workflows page and fully restarting Buzz Desktop still shows `No workflows yet`.
## Expected behavior
The newly created workflow should appear in the Workflows list and be available to view or edit.
## Additional evidence
The relay confirms that the workflow exists and is enabled:
- A workflow database record exists with the expected channel ID.
- A signed kind `30620` workflow-definition event exists with the expected `d` and `h` tags.
- The webhook executes successfully and posts its `send_message` action to the channel.
This appears to be a Desktop workflow-list/read issue rather than workflow creation or execution failing.
## Impact
The workflow is operational, but it cannot be managed through Buzz Desktop after creation.
Contributor guide
Assessment
This issue has not been assessed yet.