"Your message is too long. Please shorten it before sending"
Who are you to decide how long my messages should be? If I want to post a long stack trace, I should be able to do it.
We try to use Teams for a daily update across a broad technology group. The updates on different issues and efforts can get pretty lengthy. Teams is supposed to be an industry-wide standard, but how can it be used when messages are so limited. Now I have to break up into multiple posts. I am very disappointed in this limitation and hope it is fixed soon..
Epic failure on usability! UNBELIVEABLE that we have such an issue in 2020.
SHAME ON MICROSOFT and SHAME ON THE ENGINEERS WHO IMPLEMENTED THIS.
How do fix it from hanging??
There is a workaround for this:
- Click on Format (The A with a brush icon)
- More options (three dots icon at the end of the Format top bar)
- Code snippet
- Paste your very long text here
Ryan Pollard commented
It's so crazy that this issue is still not fixed. My devs hate Teams for this specific reason. Increase message capacity or remove the size limitations please!
Neil Raphael Veigas commented
You guys do realise that your device has limited storage space, right? The maximum message size is a healthy 25 KB. Bear with it!
Not a single resolution yet? WOW
after it locked up for me , and even with a logging out and back in. still the message was there. Locked up, but I went all the way down to the right and copied to the top left Back space and its gone.
Just hit this and its stuck and i can't communicate with the developer i was trying to give the stack trace too. I can't believe this has been an issue that has not been addressed for more than a year,
Andy Cook commented
After a lot of trial an error, I've figured out the exact length for a message to trigger the "Your message is too long. Please shorten it before sending" is 16,385 characters (at least on the desktop web app. I haven't tested mobile)
This seems to include any HTML that is wrapped around the text. If you copy and paste plain text in, it's actually longer because Teams wrapped it in the following HTML:
<div itemprop="copy-paste-block" class="copy-paste-block">
Even though "MESSAGE TEXT" is only 12 characters, Teams is actually registering the length as 78 characters.
The HTML formatting being taken into the character limit is why some "short" message might actually trigger this warning. It's very common for copied HTML to not be properly sanitized when pasted into a WYSIWYG editor like Teams has for messages.
If you're seeing this error on short, unformatted text, my suggestion would be to paste as plain text using (CTRLl/CMD + SHIFT + V). That should dramatically whittle down the length of your message.
Hope this helps! I was stumped why my shortish Adaptive Card for the integration I'm building was triggering this error, but it's because there was a lot of formatting in it causing it to go over the character limit even though the text content was short.
How to solve it? I also facing same problem
This for me makes teams almost unusable for software development! The fact that this is not fixed and the linux client is never updated makes me want to go back to Slack asap!
I see this message and I am stuck and cannot remove it. cannot correspond with the recipient any longer.
How do I fix the problem?
I deleted messages from the chain and deleted some of the photos.
I then deleted the text from the message that gave me the error, tried to send one letter, "I" and it still doesn't work.
My main issue with this is that they dont stop you from pasting a long message, then MS teams creashes, then you reboot but they think they are so smart and try to recover your message and it gets stuck again on a loop. Really silly.
What is the point of styling messages if there is a limitations to character length?? What the ****?
This is really annoying...
Ferdi Keijzer commented
2020, people have walked on the moon, there are people currently residing in a space station, we're exploring the bottom of the ocean... but I can't send more than a few lines of text in an opening message on SFB. Microsoft, please...
If you could all them to set by Team or Channel. We have some channels that we deal with failures and would like to be able to copy paste logs to only this channels. Yes we can attache file of log, but it's really about expediency and laziness sometimes.
John Pile commented
I just ran into the same problem. Only ability to fix it was cutting my message in half and posting the second half as the first "response".