Channels: Telegram, Slack and Discord
Fix pairing that won't complete, a Chief that doesn't reply in Telegram, Slack or Discord, approvals that don't arrive and voice messages that don't come back.
First checks
- Is Murage running? Channels work only while Murage is running on your computer. If the computer sleeps or Murage quits, messages aren't picked up.
- Do you have a Chief of Staff? Channels talk to your Chief only. Pairing can't start without one.
- What does the card say? Each messaging app card shows its status: Connected to Chief, Credentials saved · not paired, Connection saved · reconnecting or Connection needs attention. Choose Refresh status or Retry connection first.
Telegram
You see
The token is refusedDo this
Copy the token again from BotFather, without spaces, and choose Save token. If you're replacing a token, use Replace token with a new token for the same bot. A token for a different bot is refused. Revoke the connection first to change bots.
You see
Pairing doesn't finishDo this
- Choose Pair with Chief, then Create new pairing code.
- Choose Copy pairing command, then Open Telegram bot.
- Send the command to your bot in a private chat, not a group.
- If the code has expired, create a new one.
You see
It worked before, now it doesn't replyDo this
Your pairing reconnects by itself after Murage restarts, so you don't need to pair again. Check the card. "Telegram reported a connection problem" usually means the token was revoked in BotFather or the network is down. Refresh status, and if needed replace the token.
You see
Delivery is uncertainDo this
Murage couldn't confirm a reply arrived. Check Telegram before sending your request again, so it doesn't run twice.
You see
Approval buttons do nothingDo this
Approval requests expire after 10 minutes. Only ordinary requests and stop-line requests come to Telegram. Other reviews stay in Murage. Answer older ones in the app's Inbox.
Slack and Discord
Both need your own app: a private Slack app, or a Discord bot application.
You see
Credentials won't saveDo this
Check that every credential and ID is pasted into the right field, then choose Refresh status to see which ones were saved.
You see
Pairing could not startDo this
Check that a Chief is selected and all credentials and workspace or application details are saved. Revoke any half-finished connection with Revoke connection before trying again.
You see
Pairing code expiredDo this
Create a new pairing code and send it within its time limit.
You see
Discord rejected the Gateway session.Do this
The bot token or application settings are wrong. Check the token in the Discord developer portal, then revoke and pair again.
You see
Automatic reconnect attempts stopped.Do this
Murage gave up after several tries. Check your internet connection and that the app still has access in Slack or Discord, then choose Retry connection.
You see
No approval buttons in Slack or DiscordDo this
Typing a reply never approves. Use the Approve once or Deny buttons in a direct message with your Chief (Telegram stop-line cards also offer Allow for this task), or answer in the app, the Inbox, the menu bar or Telegram.
You see
Messages sent while Murage was stopped are missingDo this
Discord messages missed while Murage is stopped may not be recovered. Send them again once Murage is running.
You see
A long reply is cut shortDo this
Long Discord replies show as a preview, with the full result in Murage.
Voice messages
You see
My voice message gets no voice replyDo this
Voice messages work on WhatsApp. On Telegram, Slack and Discord, write to your Chief in text and ask for a voice note. Voice replies need a voice for your Chief: Flux Router, or your own voice key. Check Bot settingsVoice & alerts on your Chief. The Chief's engine also needs to be able to use Murage's tools.
You see
The voice reply is short and the rest is textDo this
Voice notes are up to about 90 seconds. Longer answers come with the detail in text.
Still stuck
- Revoke the connection, then pair again from scratch.
- Check that only one computer is running Murage with that bot token. Two installs can't share one Telegram bot.
- Collect diagnostics and report it: Collecting a bug report.
See also: Channels.
