Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,6 +1,14 @@
### **2 minutes read                                                                                                              `Intermediate`**

---
<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>


1. **Is the flow published?** If the desired result not showing while executing the flow. Make sure you have published the flow after modifying it.
1. **Check messages in all language**. If you are getting messages which you are not expecting. Please check if different messages are saved in other languages and check which language preference is user is having which you are using for testing the flow.
Expand Down Expand Up @@ -69,6 +77,19 @@ Also, make sure, that the default optin message from the Gupshup portal is disab

<img width="605" alt="image" src="https://github.com/glific/docs/assets/122982753/1393af27-b069-4d2c-b80f-61cbb6d45b7a"/>

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**.
Comment on lines +80 to +92
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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.

---

## Logs to know if any errors are thrown while executing the flow
Expand Down