1/15/2024 0 Comments Slack down right now![]() Work can get overwhelming, and so does the numerous requests from colleagues. Improve productivity during work hours with Slack’s Do Not Disturb (DND) If you just need some urgent attention or help, use - it's the same thing, but it won't send notifications to people who don't currently have Slack open. Remember that other colleagues will be in other time zones, so you don't want to trigger unnecessary notifications to them. Please don't unless it's a critical announcement no one can miss. Search for "Create a Post" and click to start writing. They're a bit hidden these days, but you can find them from the Shortcuts menu (the ⚡️ icon in the reply box, or just type "/" in the reply box). Search the Shortcuts menu to find the "Create a post" function. Treat it like people do Twitter threads, where the first message is an advertisement for what's to come in the thread: "Some thoughts on how we could reduce costs on Project A", with a threaded reply where you have the actual details. Here's a tip to encourage good behavior and your own sanity when you post to a big channel: start threads on your own messages. Threads are the antidote, keeping the clutter contained like a good foldering system. The other discussions pop up in between, and the conversation breaks down. Thread at all times, even on your own messagesĪ lot of why Slack gets overwhelming is that separate topics overlap in a channel. You can always look back at archived channels, or reopen them if discussion needs to start again - they're not deleted by Slack. Once the project is done, or the customer signed, pluck the weeds before they take over the garden. Likewise, aggressively archive single-use channels. You can always drop by to read the channel if you are curious later on. If people need you there, they'll you to bring you back. Leave channels you don't need to actively follow so they won't show up in your sidebar any time there's a new message. Just like you set up filters in email, you need to take steps to reduce noise in Slack. Managing the overwhelming volume of Slack is the key to using it correctly. No, it won't get cluttered - see the next best practice. You're creating the group DM to talk about a particular subject (a customer, project, etc.), so a channel gives you a friendly name you can use to find it later. Instead, you should make a named private channel. You'll inevitably forget someone you didn't expect to be invited. Group DMs are too hard to find later because you have to remember exactly who the members were. Learn when to use private channels and when to use Group DMs You can simply unsave them when you're done with the task. ![]() Saved items is great, because it will show you messages across all channels that you've saved. ![]() That will add it to the Saved Items list, in the top left of your channel menu. On a message, click the "." button and then the bookmark icon ("Add to saved items"). If you'd like to receive a full Root Cause Analysis (RCA) report, please reach out to to request one.Instead, you can use "Saved Items" as your to-do list. 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 |