From ae9837fcac6a3aad6bbc3079f247f968c4ea8809 Mon Sep 17 00:00:00 2001 From: AkhileshNegi Date: Sun, 28 Jan 2024 17:34:32 +0530 Subject: [PATCH] added new warning --- ...ws not working - Troubleshoot checklist.md | 42 ++++++++++++------- 1 file changed, 26 insertions(+), 16 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 a53870988..8456c6ed4 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,21 +1,21 @@ > ### **2 minutes read                                                                                                              `Intermediate`** -___ +--- + 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. -1. **Variable not defined properly.** If variables are not defined properly the flow will not give expected results. Refer [Flow level variable Vs Contact level variable](https://glific.github.io/docs/docs/Product%20Features/Flows/Flow%20Variables/Flow%20variables%20vs%20Contact%20variables/) for details about how to use variables in flows. -1. **Linked flow is not published.** The flow will not execute if any other flow is called from a flow and the other flow is not published. -1. **Web hook errors.** The flow will not give desired results if there is any error in the web hook call. Refer [How to check Webhook Logs in Glific?](https://glific.github.io/docs/docs/Product%20Features/Flows/Flow%20Actions/Call%20a%20webhook/#checking-webhook-logs) to know more about web hook logs. +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. +1. **Variable not defined properly.** If variables are not defined properly the flow will not give expected results. Refer [Flow level variable Vs Contact level variable](https://glific.github.io/docs/docs/Product%20Features/Flows/Flow%20Variables/Flow%20variables%20vs%20Contact%20variables/) for details about how to use variables in flows. +1. **Linked flow is not published.** The flow will not execute if any other flow is called from a flow and the other flow is not published. +1. **Web hook errors.** The flow will not give desired results if there is any error in the web hook call. Refer [How to check Webhook Logs in Glific?](https://glific.github.io/docs/docs/Product%20Features/Flows/Flow%20Actions/Call%20a%20webhook/#checking-webhook-logs) to know more about web hook logs. 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. ![image](https://user-images.githubusercontent.com/32592458/220824518-d36eef6e-0a58-44fd-8de5-741fa618f1f2.png) -1. **Node** **placement**- There should be only single first node at the top in flow editor. All other node should be below that. -1. +1. **Node** **placement**- There should be only single first node at the top in flow editor. All other node should be below that. -**Correct** **placement** +**Correct** **placement** ![image](https://user-images.githubusercontent.com/32592458/220824539-c8b92f3a-9a7d-43a9-9dcc-159a9211bed2.png) @@ -23,9 +23,7 @@ ___ ![image](https://user-images.githubusercontent.com/32592458/220824560-8cd4831a-9871-46b5-a664-24e8ed4bbdb2.png) - - -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. +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. 11 . **OptedOut** - check if a contact is not opted out. An easy test is to ask the contact to type optin and send it to the BOT (**Note, Your optin flow should always have optin keyword set to it**). See if it starts working. @@ -33,14 +31,15 @@ Also, make sure, that the default optin message from the Gupshup portal is disab ![image](https://user-images.githubusercontent.com/32592458/220824573-79eec9c5-d95c-49f3-9dcc-efd868d475cb.png) -## +## ![image](https://user-images.githubusercontent.com/32592458/220824585-eb9c0995-2bac-424a-b3be-1d4ab0d3d7f9.png) 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 +--- + +## 4. Errors while creating Flow image5 @@ -56,10 +55,21 @@ ___ 6. `Could not find Contact: NGO Staff` - The user created in the platform is deleted and no more exist in the platform -7. `Could not parse Group` - This looks similar to when collection added to Add to Collectionnode is deleted but in the node it is not updated. +7. `Could not parse Group` - This looks similar to when collection added to Add to Collectionnode is deleted but in the node it is not updated. 8. `Your flow has dangling nodes` - There are some nodes which are not connected to any other node in flow. -___ + +9. `Missing translations` - You will get this error when you haven’t added translation in all the nodes (but added in at least one of the nodes)- this warning message provides the node uuid which has missing translation.As one do not want to send messages in multi-languages to users & create confusion, resolving it would be important + +10. `Node Error Warning` - You will get this error if the node after the Interactive message node is not “Wait for response” as one has to allow their users to respond after sending an Interactive message. Otherwise, the flow will not proceed for the users. + Though Glific platform currently auto-creates “Wait for response” node with options, after adding Interactive message, this error is sent when someone manually removes the interactive message. + +11. `Trigger warning` - You will get this Warning if the first node of the flow is 'Send message' but without an HSM template message. While sending a flow to a collection, not necessarily all the users in the collection would be in the 24 hours session window. In such cases, if the check isn’t in place, sending messages to some of your users might fail. Hence it is important to have the 1st message as an HSM message while triggering the flow. + +12. `Media Template warning` - You will get this warning if one selected media in the attachment type while creating HSM template message, but haven’t attached any Image URL to it while adding HSM message in the flow. + +--- + ## Logs to know if any errors are thrown while executing the flow Refer [Notifications for system errors](https://glific.github.io/docs/docs/Product%20Features/Notifications#notifications-for-system-errors)