From 25734e1f53eeaf3b85e396541674aafabc7f9fae Mon Sep 17 00:00:00 2001
From: KrishnaDwibhashi2 <122982753+KrishnaDwibhashi2@users.noreply.github.com>
Date: Wed, 6 Mar 2024 14:41:41 +0530
Subject: [PATCH] Update 01. Flows not working - Troubleshoot checklist.md
(#129)
* Update 01. Flows not working - Troubleshoot checklist.md
Updated with 1 image
* Update 01. Flows not working - Troubleshoot checklist.md
Updated all images- removed 2 images which were irrelevant
---
...ws not working - Troubleshoot checklist.md | 29 ++++++++-----------
1 file changed, 12 insertions(+), 17 deletions(-)
diff --git a/docs/3. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md b/docs/3. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md
index 6a0a8477c..a8f869c17 100644
--- a/docs/3. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md
+++ b/docs/3. Product Features/03. Flows/4. Others/01. Flows not working - Troubleshoot checklist.md
@@ -1,4 +1,4 @@
-> ### **2 minutes read `Intermediate`**
+### **2 minutes read `Intermediate`**
---
@@ -10,18 +10,18 @@
1. **Flow should start with a Send a Message** - Flow should start with a message, so that it gives related message. Starting a flow with `Wait for response` action type will confuse if the flow has started or not.
1. **Ignore Keyword is checked or not? -** Check if `Ignore Keyword` is checked for the flow, which is currently executing for the contact. If Ignore Keyword is checked, then it will not allow to start another flow, if contact type any other keyword.
1. **Flow should be active** - Check if flow is inactive. Click on isActive check box and save to activate the flow.
+
+
-
-
-1. **Node** **placement**- There should be only single first node at the top in flow editor. All other node should be below that.
+9. **Node** **placement**- There should be only single first node at the top in flow editor. All other node should be below that.
**Correct** **placement**
-
+
**Incorrect placement**
-
+
10 . **Ignore keywords** - Check if contact is already in a flow, which has `ignore keywords`implemented. If contact tries to strat flow with the keyword, in this case, it will not start the flow.
@@ -29,17 +29,11 @@
Also, make sure, that the default optin message from the Gupshup portal is disabled.
-
-
-##
-
-
-
12 . **Session Window -** Check if contacts are in the session window, to start a flow with them, if not make sure the flow is started with HSM (with an expected response). The same is true if the flow is started for a collection.
---
-## 4. Errors while creating Flow
+## Errors while creating Flow : This session will show you a few errors/ warnings you might get on Glific and reason for it.
@@ -61,18 +55,19 @@ Also, make sure, that the default optin message from the Gupshup portal is disab
9. `Missing translations` - This error appears when translations are not added to all nodes (where at least one node has it). It's crucial to fix this to avoid confusing multilingual messages, and the message points out which node lacks translation.
-
+
10. `Node Error Warning` - This error shows up if the node following an Interactive message isn't a `Wait for response`. The flow won't move forward for users without allowing them to respond after an Interactive message. Even though Glific automatically adds a `Wait for response` node after the Interactive message, manual removal of this can trigger the error.
-
+
11. `Trigger warning` - This warning arises if the flow's first node is a 'Send message' without an HSM template. Without this, messages to users not in the 24-hour session window might fail. Therefore, the first message in a flow should be an HSM message.
-
+
12. `Media Template warning` - This warning indicates selecting a media attachment in an HSM template message but failing to attach an Image URL in the flow.
-
+
+
---