Home

Scrolling history slow

%3CLINGO-SUB%20id%3D%22lingo-sub-394264%22%20slang%3D%22en-US%22%3EScrolling%20history%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394264%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20appears%20to%20be%20a%20problem%20in%20both%20the%20web%20version%20as%20well%20as%20the%20desktop%20app.%20Whenever%20you%20scroll%20back%20into%20the%20messaging%20history%20(doesn't%20matter%20if%20its%20recent%20or%20not)%2C%20it%20takes%20an%20incredibly%20painful%20amount%20of%20time%20for%20the%20messages%20to%20load.%20I%20went%20to%20a%20training%20session%20recently%20where%20Teams%20was%20being%20touted%20as%20this%20end-all-be-all%20that%20was%20better%20than%20Slack%20but%20this%20one%20simple%20thing%20can't%20even%20be%20sorted%20out.%20There's%20a%20UserVoice%20post%20about%20this%20with%20230%20votes%20but%20like%20with%20any%20UV%20forum%2Fdiscussion%20topic%2C%20you%20need%20somewhere%20in%20the%20neighborhood%20of%209999%20votes%20on%20your%20topic%20for%20it%20to%20get%20any%20kind%20of%20traction%20from%20the%20development%20team%20to%20even%20read%20or%20recognize%20that%20issue%20as%20a%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeriously%2C%20Microsoft.%20You%20guys%20want%20to%20tout%20this%20as%20a%20tool%20to%20use%20for%20collaboration%20and%20you%20have%20technology%20events%20singing%20its%20praises%20but%20I%20can't%20be%20sure%20how%20you%20use%20it%20internally%20if%20this%20kind%20of%20glaring%20problem%20is%20just%20outright%20ignored%20both%20on%20the%20web%20and%20desktop%20versions.%20Its%20a%20dealbreaker%20for%20me.%20I%20can't%20imagine%20rolling%20this%20out%20to%20300%20users%20when%20only%203%20of%20us%20in%20IT%20are%20having%20this%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-394264%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-616037%22%20slang%3D%22en-US%22%3ERe%3A%20Scrolling%20history%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-616037%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F275405%22%20target%3D%22_blank%22%3E%40symm_adrian%3C%2FA%3E%26nbsp%3B%20Yes%2C%20this%20is%20indeed%20problematic.%20Anyways%20we%20can%20vote%20for%20this%20or%20ask%20Teams%20to%20look%20into%20it%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394417%22%20slang%3D%22en-US%22%3ERe%3A%20Scrolling%20history%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394417%22%20slang%3D%22en-US%22%3E%3CP%3EYup%2C%20it's%20painful%20experience%2C%20it%20loads%20the%20messages%20from%20the%20azure%20chat%20service%20and%20this%20process%20can%20definitely%20use%20some%20improvements.%20Lately%2C%20it's%20failing%20to%20even%20display%20the%20%22placeholders%22%20for%20the%20messages%2C%20so%20I%20can%20keep%20scrolling%20up%20in%20a%20completely%20blank%20screen%2C%20without%20even%20an%20indication%20that%20there%20are%20older%20messages.%20And%2030%20seconds%20later%20they%20start%20popping%20up...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-617226%22%20slang%3D%22en-US%22%3ERe%3A%20Scrolling%20history%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-617226%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F345122%22%20target%3D%22_blank%22%3E%40sbellad%3C%2FA%3E%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-617906%22%20slang%3D%22en-US%22%3ERe%3A%20Scrolling%20history%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-617906%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F345122%22%20target%3D%22_blank%22%3E%40sbellad%3C%2FA%3E%26nbsp%3Bunfortunately%20the%20problem%20with%20the%20uservoice%20feedback%20forum%20is%20that%20this%20very%20problem%20has%20been%20in%20existence%20over%20there%20for%20at%20LEAST%20two%20years%20with%20zero%20response%20from%20the%20team%20responsible%20for%20this%20product.%20Its%20tough%20to%20tell%20when%20it%20will%20ever%20get%20on%20their%20radar.%3C%2FP%3E%3C%2FLINGO-BODY%3E
symm_adrian
Occasional Contributor

This appears to be a problem in both the web version as well as the desktop app. Whenever you scroll back into the messaging history (doesn't matter if its recent or not), it takes an incredibly painful amount of time for the messages to load. I went to a training session recently where Teams was being touted as this end-all-be-all that was better than Slack but this one simple thing can't even be sorted out. There's a UserVoice post about this with 230 votes but like with any UV forum/discussion topic, you need somewhere in the neighborhood of 9999 votes on your topic for it to get any kind of traction from the development team to even read or recognize that issue as a problem.

 

Seriously, Microsoft. You guys want to tout this as a tool to use for collaboration and you have technology events singing its praises but I can't be sure how you use it internally if this kind of glaring problem is just outright ignored both on the web and desktop versions. Its a dealbreaker for me. I can't imagine rolling this out to 300 users when only 3 of us in IT are having this problem.

4 Replies

Yup, it's painful experience, it loads the messages from the azure chat service and this process can definitely use some improvements. Lately, it's failing to even display the "placeholders" for the messages, so I can keep scrolling up in a completely blank screen, without even an indication that there are older messages. And 30 seconds later they start popping up...

@symm_adrian  Yes, this is indeed problematic. Anyways we can vote for this or ask Teams to look into it? 

 

@sbellad unfortunately the problem with the uservoice feedback forum is that this very problem has been in existence over there for at LEAST two years with zero response from the team responsible for this product. Its tough to tell when it will ever get on their radar.