I ticked the "Available For Reminders" checkbox on a saved search for a Custom Record type, and added it to my Reminders portlet, but whenever I do, the portlet goes blank, then I refresh it, and the new saved search is not in it, and so I try to add it again, with the same result. It won't really let me add it, it only pretends to let me add it. Are Custom record types not supported for Reminders? If so, then why would it let me tick the "Available For Reminders" checkbox on a Saved Search that's for a custom record type?

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that there are a few potential reasons why your saved search for a custom record type is not appearing in the Reminders portlet, even though you have ticked the "Available For Reminders" checkbox. 1. Permissions: Even though the user created the search and set it as "Available for Reminders", there might be some permission issues preventing it from showing up in the Reminders portlet. Make sure the user has the necessary permissions to view the search. 2. Summary Searches: Summary saved searches do not always work well with reminders and can provide inconsistent results. If your saved search is a summary search, this could be the reason why it's not showing up in the Reminders portlet. 3. Custom Record with "No Permission Required": If it's a custom record with "No Permission Required", try adding the permission to the custom records permissions. 4. Refresh the Portlet: Make sure to refresh the portlet. Sometimes, the portlet might not update immediately after changes are made. 5. Run Unrestricted: Try running the search unrestricted. As for your question about whether custom record types are supported for Reminders, there doesn't seem to be any explicit mention in the conversations that they are not supported. However, the issues you're experiencing might be due to the reasons mentioned above. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******