diff --git a/docs/4. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md b/docs/4. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md
index a8f869c17..736a4ac1b 100644
--- a/docs/4. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md
+++ b/docs/4. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md
@@ -1,6 +1,14 @@
-### **2 minutes read `Intermediate`**
----
+
+
+
+
5 minutes read
+
Level: Intermediate
+
Last Updated: February 2026
+
+
+
+
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.
@@ -69,6 +77,19 @@ Also, make sure, that the default optin message from the Gupshup portal is disab
+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**.
---
## Logs to know if any errors are thrown while executing the flow