Revise HSM Template Message Error documentation

[SangeetaMishr]

Updated the HSM Template Message Error documentation to include new troubleshooting steps and key points regarding message delivery issues and frequency capping.

Summary by CodeRabbit

• Documentation
  • Enhanced HSM Template Message troubleshooting with new guidance on message delivery issues related to frequency capping
  • Improved documentation header with helpful metadata including estimated read time, knowledge level, and last updated timestamp
  • Added detailed recommendations on retry strategies and best practices for managing rate-limited messages

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation updates to HSM Template Message Error guide: refreshed the introductory header metadata and added a new troubleshooting section detailing Meta's frequency capping requirements, dynamic blocking mechanisms, and recommended retry wait periods with external resource references.

Changes

Cohort / File(s)	Summary
Documentation Update docs/4. Product Features/10. Others/HSM Template Message Error.md	Updated introductory header with concise metadata (10 minutes read, Level: Beginner, Last Updated: January 2026). Added new troubleshooting item covering Meta's frequency capping behavior, including dynamic blocking, retry guidance, and external resource links.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Suggested reviewers

• mahajantejas
• Fawas003

Poem

🐰✨
Docs we polish, words we mend,
HSM troubles, guides we send,
Meta's capping, now made clear,
Twenty-four hours, patience dear!
Hop hop — clarity's here! 📚

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: revising documentation for HSM Template Message Error with new troubleshooting content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch HSM

Tip

🧪 Unit Test Generation v2 is now available!

We have significantly improved our unit test generation capabilities.

To enable: Add this to your .coderabbit.yaml configuration:

reviews:
  finishing_touches:
    unit_tests:
      enabled: true

Try it out by using the @coderabbitai generate unit tests command on your code files or under ✨ Finishing Touches on the walkthrough!

Have feedback? Share your thoughts on our Discord thread!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🚀 Deployed on https://deploy-preview-563--glific-docs.netlify.app

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docs/4`. Product Features/10. Others/HSM Template Message Error.md:
- Around line 45-46: The documentation currently links the anchor text "Per-User
Marketing Template Message Limits" to the Facebook "error-codes" page, which is
incorrect; update the link in the sentence that contains the Gupshup blog and
the "[Per-User Marketing Template Message Limits]" anchor so it either (a)
replaces the URL
(https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes)
with the correct Facebook Developers page that documents per-user
marketing/template message limits for WhatsApp, or (b) change the anchor text to
accurately describe the linked page (e.g., "WhatsApp error codes") if you intend
to keep the error-codes URL; ensure the anchor text and target URL match.

🧹 Nitpick comments (2)

docs/4. Product Features/10. Others/HSM Template Message Error.md (2)

1-9: Consider improving table accessibility.

The header table lacks semantic markup for accessibility. Consider using <th> elements for the header row or adding ARIA labels to improve screen reader support.

♿ Suggested accessibility improvements

 <h3>
  <table>
   <tr>
-    <td><b>10 minutes read</b></td>
-    <td style={{ paddingLeft: '40px' }}><b>Level: Beginner </b></td>
-    <td style={{ paddingLeft: '40px' }}><b>Last Updated: January 2026</b></td>
+    <th scope="col">10 minutes read</th>
+    <th scope="col" style={{ paddingLeft: '40px' }}>Level: Beginner</th>
+    <th scope="col" style={{ paddingLeft: '40px' }}>Last Updated: January 2026</th>
   </tr>
 </table>
 </h3>

---

48-48: Remove hardcoded image dimensions for responsive design.

The image has fixed width="921" height="717" attributes that may not scale well on mobile devices or different screen sizes. Consider removing these attributes and letting CSS handle responsive sizing.

📱 Proposed fix for responsive images

-<img width="921" height="717" alt="image" src="https://github.com/user-attachments/assets/e897a19f-1c41-4913-9052-f5025cfc5e7e" />
+<img alt="image" src="https://github.com/user-attachments/assets/e897a19f-1c41-4913-9052-f5025cfc5e7e" />

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify that the external URLs are accessible and return valid responses

echo "Checking Gupshup blog URL..."
curl -I -s -o /dev/null -w "HTTP Status: %{http_code}\n" "https://www.gupshup.ai/resources/blog/all-you-need-to-know-about-whatsapp-business-api-frequency-capping/"

echo -e "\nChecking Facebook developers URL..."
curl -I -s -o /dev/null -w "HTTP Status: %{http_code}\n" "https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes"

Repository: glific/docs

Length of output: 154

---

🏁 Script executed:

#!/bin/bash
# Fetch the Facebook URL content to verify it covers "Per-User Marketing Template Message Limits"
echo "Fetching Facebook developers page content..."
curl -s "https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes" | head -c 3000

Repository: glific/docs

Length of output: 3100

---

🏁 Script executed:

#!/bin/bash
# Search for mentions of "marketing template" or "per-user" in the error codes page
echo "Checking for marketing template or per-user limits content..."
curl -s "https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes" | grep -i -E "(marketing|per-user|template.*limit|frequency.*cap)" | head -20

Repository: glific/docs

Length of output: 50368

---

Correct the Facebook developers link—it points to error codes, not template message limits.

The Facebook developers link is accessible but incorrect. The page titled "Error codes" (documenting WhatsApp Business Platform Cloud API error codes and solutions) does not cover "Per-User Marketing Template Message Limits" as stated in the documentation. Either replace the link with the correct Facebook developers page covering template message limits, or update the text to reflect what the error-codes page actually contains. The Gupshup blog link is correctly accessible.

🤖 Prompt for AI Agents

In `@docs/4`. Product Features/10. Others/HSM Template Message Error.md around
lines 45 - 46, The documentation currently links the anchor text "Per-User
Marketing Template Message Limits" to the Facebook "error-codes" page, which is
incorrect; update the link in the sentence that contains the Gupshup blog and
the "[Per-User Marketing Template Message Limits]" anchor so it either (a)
replaces the URL
(https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes)
with the correct Facebook Developers page that documents per-user
marketing/template message limits for WhatsApp, or (b) change the anchor text to
accurately describe the linked page (e.g., "WhatsApp error codes") if you intend
to keep the error-codes URL; ensure the anchor text and target URL match.