> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tightknit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Known Issues

### Shortcuts Rate Limited

*First reported:* May 29, 2025

For customers that installed the Tightknit app on or after May 29, 2025, the following limitations apply:

* The **[Post to site](/slack/shortcuts-and-commands/message-shortcuts#tightknit-shortcuts)** message shortcut is limited to 1 use per minute across all admin users in the workspace
  * The same limitation applies to the **Post to site** action within the **[Manage Content](/slack/shortcuts-and-commands/message-shortcuts#tightknit-shortcuts)** message shortcut
* The **[Post to site](/slack/shortcuts-and-commands/message-shortcuts#tightknit-shortcuts)** message shortcut will include up to a maximum of 15 replies in the thread as comments on the post
* The "Find related discussions" action of the **[Admin Experimental](/slack/shortcuts-and-commands/message-shortcuts#tightknit-shortcuts)** shortcut will analyze up to a maximum of 15 replies in a thread and is limited to 1 user per minute across all admin users in the workspace

<Note>
  **Why is this happening?** <br />
  Slack has implemented rate limits for apps distributed outside of the Marketplace. To read more, visit: [https://api.slack.com/changelog/2025-05-terms-rate-limit-update-and-faq](https://api.slack.com/changelog/2025-05-terms-rate-limit-update-and-faq).
</Note>

### Miscellaneous

* If the [New Post Notification Agent](/channels-and-feeds/agent-settings#new-post-notification-agent) is enabled in a channel, Tightknit may fail to cleanup and remove the agent's message if the parent Slack message is deleted or removed from the community site.
* If a user has the feed open in their browser when a new post comes in, the references within the post body (e.g., user mentions, channel links) may not get initially populated. Instead they may see placeholders such as `[private user]`. Refreshing the page will resolve the issue. Users that arrive on the page after the post as been made will not experience this issue.


## Related topics

- [Salesforce](/integrations/salesforce.md)
- [Single sign-on (SSO)](/community-site/sso.md)
- [SOC 2 Compliance](/security/soc-2.md)
- [Tightknit Infrastructure & Application Security](/security/application.md)
- [Vulnerability Disclosure Policy](/security/vulnerability-disclosure.md)
