Messages in channels and for entries
"Sending failed", "Capturing failed", "The history could not be loaded", "Today could not be loaded" – what the messages in the chat mean.
Updated on
chat, message, history, rule, member, filingMessages from channels, the history and “Today”.
“Sending failed.” / “Capturing failed.” / “Reply failed.”
- Cause: The message did not reach the server – connection gone, session expired, or you are no longer a member of the channel.
- Fix: Your text stays in the composer. Check the connection, send again. If relais.io asks for a code, sign in and then send.
“Saving failed.” / “Deleting failed.”
- Cause: Editing and deleting only work for your own messages and only as long as the channel has no rule against it.
- Fix: Check the rules in the channel header. Other people’s messages can only be changed by them.
“The history could not be loaded.” / “Loading more failed.”
- Cause: The channel is unreachable or you no longer have access (visibility set to “Private”, unit changed).
- Fix: Reload the page. If the channel is missing from the sidebar afterwards, ask the responsible unit for an invitation.
“Today could not be loaded.”
- Cause: Your personal inbox is temporarily unreachable.
- Fix: Reload. The events are not lost – they catch up on the next load.
“Filing failed.”
- Cause: The target channel was deleted in the meantime or you are not a member there.
- Fix: Choose another channel or become a member first.
“Creating failed.” (channel)
- Cause: Name missing, unit missing, or a channel with the same short form already exists in this unit.
- Fix: Change the name or choose another unit.
“The member could not be added.” / “The rule could not be added.”
- Cause: Channel settings can only be changed by whoever may decide in the responsible unit.
- Fix: Check permissions or ask the responsible unit.
“Confirming failed.”
- Cause: You confirm rules per version. If the rule was just changed, your confirmation went to the old version.
- Fix: Open the rules again and confirm the current version.
“Rejected — the reason is in the thread.”
- Cause: Not an error: an approval or a request by an agent was rejected. The person who decided left the reason in the thread.
- Fix: Open the thread; request an exception if needed.