Revise troubleshooting checklist and add infinite loop info#573
Revise troubleshooting checklist and add infinite loop info#573SangeetaMishr wants to merge 1 commit intomainfrom
Conversation
Updated the reading time, level, and last updated information in the troubleshooting checklist. Added details about infinite loop detection in flows.
📝 WalkthroughWalkthroughDocumentation update to a troubleshooting guide adds detailed specifications for detecting infinite loops in flows, including two distinct threshold conditions (Same Node, Different Messages at threshold 5; Same Node, Same Message at threshold 3), along with updated metadata reflecting a 5-minute read time and February 2026 last updated date. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
|
🚀 Deployed on https://deploy-preview-573--glific-docs.netlify.app |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/4`. Product Features/03. Flows/4. Others/01. Flows not working -
Troubleshoot checklist.md:
- Around line 80-92: The nested list indentation is inconsistent: the "Same
Node, Same Message" sub-item uses 2 spaces before the dash while the "Same Node,
Different Messages" sub-item uses 3; update the "Same Node, Same Message" list
block (the lines under that heading) to use the same 3-space indentation before
the dash so both nested list items are aligned and satisfy markdownlint-cli2;
ensure the threshold/action lines under "Same Node, Same Message" maintain the
same indentation pattern as the first sub-item.
🧹 Nitpick comments (1)
docs/4. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md (1)
2-10: Consider CSS classes or semantic markdown for better maintainability.The inline styles work functionally but make the documentation harder to maintain. If your documentation system supports CSS classes or a more semantic approach, consider refactoring this metadata section.
♻️ Optional refactor: Use CSS classes if supported
-<h3> - <table> - <tr> - <td><b>5 minutes read</b></td> - <td style={{ paddingLeft: '40px' }}><b>Level: Intermediate </b></td> - <td style={{ paddingLeft: '40px' }}><b>Last Updated: February 2026</b></td> - </tr> -</table> -</h3> +<h3 class="doc-metadata"> + <table> + <tr> + <td><b>5 minutes read</b></td> + <td class="metadata-spacing"><b>Level: Intermediate </b></td> + <td class="metadata-spacing"><b>Last Updated: February 2026</b></td> + </tr> +</table> +</h3>Or use semantic markdown if your system supports frontmatter:
--- reading_time: 5 minutes level: Intermediate last_updated: February 2026 ---
| 13. `Infinite loop detected` - The system monitors nodes (node_uuid) for repeated triggers and message bodies (body). Infinite loops are detected using two thresholds: | ||
|
|
||
| - Same Node, Different Messages | ||
|
|
||
| > - **Condition:** A node is triggered multiple times with different message bodies. | ||
| > - **Threshold:** 5 times | ||
| > - **Action:** After the 5th different message hits the same node, the system flags it as an **infinite loop**. | ||
|
|
||
| - Same Node, Same Message | ||
|
|
||
| > - **Condition:** A node is triggered multiple times with the same message body. | ||
| > - **Threshold:** 3 times | ||
| > - **Action:** After the 3rd repetition of the same message at the same node, the system flags it as an **infinite loop**. |
There was a problem hiding this comment.
Fix indentation inconsistency in nested list.
The second sub-item (line 88) has inconsistent indentation compared to the first sub-item (line 82). Line 82 uses 3 spaces before the dash, while line 88 uses 2 spaces. This causes a markdownlint warning and may affect rendering.
🔧 Proposed fix for indentation
- Same Node, Different Messages
> - **Condition:** A node is triggered multiple times with different message bodies.
> - **Threshold:** 5 times
> - **Action:** After the 5th different message hits the same node, the system flags it as an **infinite loop**.
- - Same Node, Same Message
+ - Same Node, Same Message
> - **Condition:** A node is triggered multiple times with the same message body.
> - **Threshold:** 3 times
> - **Action:** After the 3rd repetition of the same message at the same node, the system flags it as an **infinite loop**.As per coding guidelines, markdownlint-cli2 flagged inconsistent indentation for list items at the same level (expected 3 spaces, actual 2 spaces at line 88).
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)
[warning] 88-88: Inconsistent indentation for list items at the same level
Expected: 3; Actual: 2
(MD005, list-indent)
🤖 Prompt for AI Agents
In `@docs/4`. Product Features/03. Flows/4. Others/01. Flows not working -
Troubleshoot checklist.md around lines 80 - 92, The nested list indentation is
inconsistent: the "Same Node, Same Message" sub-item uses 2 spaces before the
dash while the "Same Node, Different Messages" sub-item uses 3; update the "Same
Node, Same Message" list block (the lines under that heading) to use the same
3-space indentation before the dash so both nested list items are aligned and
satisfy markdownlint-cli2; ensure the threshold/action lines under "Same Node,
Same Message" maintain the same indentation pattern as the first sub-item.
1 participant
Updated the reading time, level, and last updated information in the troubleshooting checklist. Added details about infinite loop detection in flows.
Summary by CodeRabbit
Documentation