Messages too large, too many pictures, uploads
A message was not sent, some pictures were left out, an attachment was refused, or a bot could not upload a file in the built-in browser. The limits, and the way round each one.
A message was not sent
You see
Not sent: this message is {size}, and one message can be up to {limit}. Shorten it or split it into smaller messages. Your text is still here.Do this
One message can hold about 1 MB of text. That is a few hundred pages, so this usually means a pasted file. Save the text as a file in the bot's working folder and ask the bot to read it, or split it across messages.
You see
Not sent: Murage refused this message because it is too large. Shorten it or split it into smaller messages. Your text is still here.Do this
Same limit, caught on the other side. Shorten it or put the text in a file.
You see
This message could not start, so it was not sent. Your words are still here. Send it again when you are ready.Do this
The bot could not pick the message up. Wait a moment and choose Send again.
You see
This message may not have reached the bot before Murage closed. It was not sent again. Send it again if you still want it.Do this
Murage closed while the message was on its way and did not send it a second time on its own, so you never get a duplicate. Read it over and send it again if you still want it.
You see
The bot could not take that message in time and a newer one had already gone ahead, so it was not run. Send it again if you still want it.Do this
You sent two messages close together and the second won. Send the first again if it still matters.
You see
Earlier messages are still being delivered. Your message is back in the box. Send it again in a moment.Do this
Give it a few seconds, then Send again.
You see
Your words are still here. This device could not record the send, so nothing went out. Press Send again in a moment.Do this
Seen on a phone or another paired device when the connection dropped mid-send. Nothing went out. Press Send again.
You see
Your words are still here. Murage could not yet confirm whether your earlier message arrived. Press Send again in a moment.Do this
The connection came back before Murage could check. Press Send again; if the earlier one did arrive, Murage tells you and keeps your edited words as a new message.
You see
Held: an image is still uploading. Sending now would attach it to your next message instead. Press Enter again once the attachment appears.Do this
Wait for the thumbnail, then press Enter.
Pictures
One message carries up to 10 pictures, 10 MB each and 15 MB together. Pictures past that are left out of what the bot receives, and you get one plain line in the chat saying so. Send fewer per message, or shrink them first. A phone photo is often 4 to 6 MB, so three or four of them can hit the 15 MB line before you hit ten.
Disk space
Every new attachment, and every copy into Files, leaves at least 1 GB of space on the disk. When there is less than that, or Murage cannot read how much is left, the attachment is refused.
You see
Your computer is almost out of disk space, so Murage could not save this.Do this
Clear space on the drive Murage runs from, then attach the file again. Do not turn the limit off by moving Murage to a fuller disk; the 1 GB floor is what keeps the database writable.
You see
Murage could not check this disk, so it did not save the attachmentDo this
Usually a network drive or an external disk that was busy. Try again. If it keeps happening, move Murage's data to a local drive.
Uploads in the built-in browser
A bot in the built-in browser cannot upload a file to a website. When a page opens a file picker, Murage cancels it and tells the bot that uploads are not supported yet, so the bot knows to hand that step to you.
Three ways round it:
- Ask the bot to get the file ready in its working folder, then choose Take control in the bot's browser and do the upload yourself. Choose Return to bot when you are done.
- Use a connected app that takes the file directly, such as the service's own API through connected apps.
- Set the bot's computer to a Local VM and ask it to do the upload on that desktop, which has a full browser with a working file picker.