Update reading time and add troubleshooting guide

[SangeetaMishr]

Updated reading time and last updated date in the documentation. Added a troubleshooting guide for contacts not appearing in collections.

Summary by CodeRabbit

• Documentation
  • Added a new troubleshooting guide addressing contact not being added to collections, with step-by-step checks for collection nodes, flow reachability, and name validation.
  • Updated documentation metadata including estimated read time and last updated timestamp.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation update adding metadata changes and a new troubleshooting guide section for contact collection issues. The troubleshooting content appears duplicated in the document, requiring verification of intended placement.

Changes

Cohort / File(s)	Summary
Documentation Update docs/4. Product Features/10. Others/06. Collections.md	Updated read time (5→7 min) and last modified timestamp (October 2025→February 2026). Added "Contact Not Added to Collection – Troubleshooting Guide" section with multi-step diagnostic checks including node presence, flow reachability, collection validation, and publish status verification. Section content duplicated in document.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• Update 08. Add or Remove the contact to a collection.md #387: Updates documentation for the Add/Remove contact-to-collection feature with publish, removal, and verification steps, directly related to this troubleshooting guide addition.

Suggested reviewers

• Fawas003

Poem

🐰 Collections flow through documents clear,
Troubleshooting guides appear (twice, I fear!),
With metadata fresh and timestamps new,
The rabbits hop through guides both old and true. 🌟

🚥 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 clearly summarizes the two main changes: updating reading time metadata and adding a troubleshooting guide section to the Collections documentation.
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 Collection.md

---

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-580--glific-docs.netlify.app

[coderabbitai]

🧹 Nitpick comments (1)

docs/4. Product Features/10. Others/06. Collections.md (1)

268-329: Strong troubleshooting addition; consider consistent inline formatting for node names.

This section is clear and actionable. Optional polish: format repeated UI/node labels like Add to Collection, Remove from Collection, Published/Draft as inline code for consistency and faster scanning.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/4`. Product Features/10. Others/06. Collections.md around lines 268 -
329, The doc uses UI/node labels inconsistently—please wrap repeated interface
labels like "Add to Collection", "Remove from Collection", "Published", and
"Draft" in inline code formatting throughout this section (every occurrence in
headings, bullet points, and steps) to improve scanning and consistency; update
the lines that mention node names and status labels so they appear as inline
code wherever they reference UI elements or node names.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/4`. Product Features/10. Others/06. Collections.md:
- Around line 268-329: The doc uses UI/node labels inconsistently—please wrap
repeated interface labels like "Add to Collection", "Remove from Collection",
"Published", and "Draft" in inline code formatting throughout this section
(every occurrence in headings, bullet points, and steps) to improve scanning and
consistency; update the lines that mention node names and status labels so they
appear as inline code wherever they reference UI elements or node names.

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c5d1dec and 8a705e7.

📒 Files selected for processing (1)

• docs/4. Product Features/10. Others/06. Collections.md