-
Start with one specific post. Suppose a member submits “Saturday bike repair meetup at 10; bring a photo of the problem,” and it remains pending. Note the submission time and member, then check the Group’s post-approval settings. Is approval required for every member post, or does this member have a different approval status? If all comparable posts wait for an admin, this may be the normal queue rather than a keyword-rule issue.
-
Check Admin Assist activity for that post. In the Group’s admin tools, look for an action around the submission time and read the rule or reason shown, if one is available. A match on “repair” would be useful evidence; the word appearing in the post by itself is not. Also distinguish an action that held the post from one that declined it, since the next check differs.
-
Open the moderation queue. Find the post under Pending posts or the relevant moderation view, and check its displayed status and any reason or flag. Compare it with one other pending post submitted under similar conditions. If neither has a rule action and both are waiting for approval, changing a keyword rule is unlikely to clear that bottleneck. If the example post has a specific Admin Assist action, inspect that rule before changing anything broader.
-
Make the smallest change the evidence supports. If a rule caught ordinary event wording, narrow that rule and watch for the next comparable submission. If it is routine approval, address queue coverage instead. When the UI gives no clear reason, record that uncertainty rather than assigning a cause.
How do other Group admins tell an automated hold from an ordinary approval delay when the queue labels are ambiguous?