![]() Use it to mark your outside-of-work hours. Reduce off-hours pings with Do Not DisturbĪnother way to limit untimely interruptions is to use the built-in DND feature. To see who responded to a message with a particular emoji, mouse over it on desktop or long-press the reaction on mobile. Multiple messages means multiple interruptions, and that’s far from an ideal use of everyone’s time and attention. Getting everything you need into a single direct message means that only one notification is sent to the person. You can start a DM with “hey” or with a □, but make it the first line of your entire message. The person might see the indicator that you’re typing but is still left waiting for your full message. ![]() Here’s a quick win: Never send a direct message that just says “hey” or “hello.” Even if you immediately follow up with your “real” message, the recipient gets a notification on that first “hey” that contains no information and potentially causes distraction. Less messages means more efficient collaboration Thankfully, there are a few basic steps every team can take to reduce notifications while keeping communication open. And when you’re away from Slack for any length of time, those notifications can really stack up. Every DM results in a notification on the mobile and desktop devices of your recipient.So if someone asks you a question over one, others on your team may do the same later on without knowing you already answered it. If you'd like to receive a full Root Cause Analysis (RCA) report, please reach out to to request one.Slack works best as a collaborative workspace when everyone in a company uses it to have transparent, informative discussions in channels, which are organised around projects, teams and disciplines.īut let’s be honest, many teams rely far too often on direct messages-mostly for quick questions and answers. We continued to closely monitor the situation until we had full confidence the issue was resolved and no further impact would reoccur. By 9:14 AM PST, everyone should have been able to connect to Slack again after reloading their app or browser tab. This allowed the system to recover while steadily restoring full access to all users. With traffic distributed across the additional databases, we gradually lifted the rate limits to allow more people to connect to Slack. We reinstated the rate limits and redirected some traffic to the database replicas to relieve the demand on our primary databases. ![]() However, we moved too quickly and the increased activity affected the system again. Once the system had stabilized, we began lifting these rate limits to enable more connections to Slack. This meant that some people could not access Slack at all, but also that Slack would continue working for those who were already connected. We introduced tighter rate limits on connection requests to reduce the load on the system. Due to this increased activity, the affected databases failed to serve incoming requests to connect to Slack. ![]() On Februfrom 6:00 AM PST to 9:14 AM PST, customers may not have been able to access Slack.Ī configuration change inadvertently lead to a sudden increase in activity on our database infrastructure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |