"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.
Anonymous
shared this idea
58 comments
-
Anonymous
commented
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">
MESSAGE TEXT
</div>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.
-
Aea
commented
How to solve it? I also facing same problem
-
Derek
commented
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!
-
Hanan
commented
I see this message and I am stuck and cannot remove it. cannot correspond with the recipient any longer.
-
Anonymous
commented
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. -
eliezer
commented
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.
-
Anonymous
commented
What is the point of styling messages if there is a limitations to character length?? What the ****?
-
Anonymous
commented
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...
-
Doug
commented
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".
-
David Emmerson
commented
This didn't happen in the free, public version of Skype, what idiot decided it was a clever thing to do in SFB?
-
Mike G
commented
Ankit Jadia is the hero here. For convenience, here's the workaround he posted earlier in the comments. I don't know why Microsoft can't at least include this workaround with their disappointing error msg.
---------------------------------
Ankit Jadia commented · October 16, 2019 05:38
Just try sending a simple "Hi" first and then paste your long message and send it. It will work. :)
----------
A small explanation about why this works. Skype for Business usually sends messages as thread bubbles in groups. So when first message is being sent from your side to other party it cannot be very long. Once you send a small message like "Hi" or something and then if you send the long one it gets clubbed in a group and you won't face any problem. -
Chris C
commented
This is the first thing that happened to me when I used teams after previously having used slack at another organisation. This is classic Microsoft. Cripple software right out of the gate so it just makes a horde of angry users. The epic amount of errors I deal with daily, be it visual studio, office 365, azure etc has been steadily growing. I don't understand how such a supposedly successful company regularly treats its users like braindead cattle.
-
Johannes Hejslet Jørgensen
commented
Our company wants us to switch from Slack to Teams..
So I started testing it with the last message I sent on Slack. It's a SQL result with 269 lines.
This worked seamlessly on Slack where it automatically opened dialog to fix the long message issue.
In Teams I had to search the web to see how to format the SQL code but I have not found a solution for posting the long message. -
Anonymous
commented
We cannot control user permission in teams. if we want to assign one user to chat with only particular personal but this feature not available in MS teams.
-
Stephanie Parker
commented
@Ankit Jadia- we get this error no matter if it's an existing thread (reply) or new thread.
-
Ankit Jadia
commented
Just try sending a simple "Hi" first and then paste your long message and send it. It will work. :)
Edit 1:
----------
A small explanation about why this works. Skype for Business usually sends messages as thread bubbles in groups. So when first message is being sent from your side to other party it cannot be very long. Once you send a small message like "Hi" or something and then if you send the long one it gets clubbed in a group and you won't face any problem. -
Kurt Zalmstra
commented
Getting the issue here also. This is a horrible error and something that should not happen. From what I can see there is no documentation around character limits however there is a hard limit somewhere. Please at least let us know what the limits are.
