Support
Help with Dispatched: troubleshooting, bug reports and feature requests.
hello@horizon-tech.io. We usually answer within two working days.
Bugs and feature requests
Open an issue on GitHub. Include the version (in Settings, or dispatched --version), your operating system, and what you expected to happen.
Never paste connection strings, keys or message contents into an issue. The activity log (dispatched activity export) holds no secrets and can help.
Troubleshooting
Signing in with Entra ID lists no namespaces
Listing namespaces needs a role on the subscription or resource group that lets you read them (Reader is enough). Reading messages also needs a Service Bus data role on the namespace or entity: Azure Service Bus Data Receiver to peek and receive, Data Sender to send, or Data Owner for both and for managing entities.
A connection string works for some actions and not others
A shared access policy grants Listen, Send or Manage. Peeking needs Listen, sending needs Send, and listing or changing entities needs Manage. In the CLI, dispatched profile test shows which rights work for a saved connection.
Behind a proxy, or port 5671 is blocked
Set the connection's transport to WebSockets (port 443), and add a proxy in its settings if needed.
A queue I just created shows "not found"
Azure takes a few seconds to make a new entity available; refresh after a moment.
Messages keep returning to the dead-letter queue
Check the dead-letter reason before resubmitting: see how to repair dead-lettered messages.