"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
30 comments
-
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.
-
Charles Chang
commented
Hello, we are getting this same error as well. Our developers are sending code to each other via teams (not email to Teams) and getting this error (see attached). We are in the process of moving people from Slack to Teams and now they will go back to Slack until this gets fixed. I just opened a MS ticket and they said they are aware of the issue but no ETA. Can this be resolved ASAP?
-
Joel Leichty
commented
Two things:
1. This error message (also "You'll need to shorten this message to send it") is a weak error message. Shorten it by how much? Tools like Twitter have a visual indicator of how much over it is.
2. The length of the message I believe is counting hyperlinks, not the viewable text. Hyperlinks can be really long and therefore this restriction is way too small. -
LutzHH
commented
I doubt that this is really the error message is connected to the correct problem teams is having. Maybe it is a special character? We have been using Teams without any of these problems for month and now I suddenly had this message with very little content.
-
Justin H
commented
As of 2019-03-11, it seems the mobile app clients (Android 1416/1.0.0.2019021309) have shorter char limits than the Desktop client. I only found out about this when I lost half of my message after editing it on my mobile phone.
If there is a char limit per message, Microsoft should clearly prompt the user and explain the limit (whether it's number of char, or number of KB, etc) in https://docs.microsoft.com/en-us/microsoftteams/limits-specifications-teams.
Loosing content is not a good user experience to win over users from Outlook and Skype for Business.
-
Sydney Lacey
commented
This is a frustrating problem. I'm forwarding emails to a Team account and they are often considered "too long" and end up as an embedded link that users must then click to open the entire email message. Any perceived "extra steps" for end users lessens the utilization of our Team site. The whole idea is to show them that they don't have to rely on emails and that their habit of keeping every email they've ever been sent in their inbox is counterproductive in the long run. If I'm sending/forwarding emails or posting to our Team site directly, I know to remove unnecessary images and text to cut down on the word count but if my bosses can't get their messages to "fit" the secret word count for Teams... they are going to keep using emails.
-
Anon
commented
Why is this still such a problem in 2018? Seriously, if not for my organization shoving it down my throat I would never use this ****** app
-
Ben
commented
Me too. Every stack trace I post is always "too long." Very annoying when trying to collaborate amongst app developers, QA's, and Ops.
-
Anonymous
commented
One year later and this is still open? In addition, that message stays FOREVER regardless of the subsequent messages you try to send. How can I remove it? Only solution I found so far is closing and reopening Teams.