From Monday August 29 at 10:11 AM PDT to Wednesday August 31st at 12:42 PM PDT, some Grid customers were running into errors when configuring SSO settings for their workspaces. Upon investigation, we identified an issue that was resulting in empty SAML configuration files. These empty files triggered the errors seen by users.
Removing the offending file fixed the issue for all affected users.
3:32 PM PST
We've rolled out a fix and SSO configuration is now working as expected. Thank you for your patience while we sorted out this issue.
1:38 PM PST
We're continuing to investigate the issue regarding some Enterprise Grid customers seeing errors when attempting to set up SSO on their org.
We'll post an update just as soon as we have more information to share. Thank you for your continued patience.
8:22 AM PST
Some Enterprise Grid customers may see errors when attempting to set up SSO on their org. This does not appear to impact existing SSO configurations at this time.
We’re investigating and will let you know as soon as we know more. We appreciate your patience in the meantime.
7:53 PM PST
From August 29, 2022 at 11:26 AM PDT to August 30, 2022 at 3:56 PM PDT, some customers may have experienced issues with their Mark as Read preferences, and intermittent issues loading channel history.
When you view a channel, Slack remembers your last scroll position so we can take you back to the same place. A recent feature update inadvertently bypassed the check for this scroll position, creating the impression that Slack wasn't respecting your Mark as Read preference. Additionally, this incorrectly prevented channel history from loading for some users.
We identified the root cause and rolled this code change back, resolving the issue for all affected customers.
7:40 PM PST
We've resolved the issue, and all impacted customers should have their Mark as Read preferences restored. You'll need to reload Slack (Cmd/Ctrl + Shift + R) to see the fix on your end. Thanks for bearing with us and we apologize for keeping you away from your work.
2:37 PM PST
We’re still investigating this issue, but we don’t have additional information just yet. We're so sorry for the interruption! If we find out more, we’ll let you know.
1:22 PM PST
Some users are reporting their Mark as Read preferences are not being respected. Users may be able to manually update their preferences to restore them back to their expected state.
Our engineering team is currently investigating and we'll provide an update as soon as one is available. Sorry for any disruption this may cause.
8:16 AM PST