Sleep/Delay

[Ramesh Krishnamoorthy]

Is there a way to introduce an artificial delay/sleep in the conversational flow? I remember seeing something in those lines but unable to find it anymore. 

We want to introduce a delay of few secs at specific points in the flow. Possible?

Thanks in advance

[Ian Lawrence]

Hi

You can use a Wait for Response and Continue after waiting (see image). We use this to make sure all media has loaded and to prevent messages getting out of sync

The issue you might find is that the minimum wait time is 1 minute so we just break out of it if the user sends any message. If it becomes an issue as we are scaling we might patch this to allow more granular wait times

Regards

--
You received this message because you are subscribed to the Google Groups "rapidpro-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rapidpro-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rapidpro-dev/8a3c7a4c-f502-4134-ac23-4a16884ba733n%40googlegroups.com.

--

Ian Lawrence 

Jozian Ltd is a company registered in England and Wales. Registered offices: 13-15 Commercial Road, Hayle Cornwall UK TR27 4DE 

Company No. 7532806  

[Ramesh Krishnamoorthy]

Cool. Thanks for the response Ian. Will give it a try and reach out to you if more clarifications are required. Thanks

[Eric Newcomer]

Just a heads up that it is not recommended to reduce the wait times below one minute. 

There’s been discussion around intentional outbound delays. 

https://github.com/rapidpro/rapidpro/issues/875

To view this discussion on the web visit https://groups.google.com/d/msgid/rapidpro-dev/03d5acb4-95d2-4196-b30f-fa327290df41n%40googlegroups.com.

[Donald Lobo]

We ran into the same issue, and in Glific, we introduced a Wait for Time node to make it easier for our NGOs to introduce delay, A lot easier for them to understand :)

lobo

[Eric Newcomer]

To summarize, the current thinking is that to instead introduce a "be more human" checkbox at the channel level, not having to instrument it for every response. This feels like a more natural fit and would avoid aggressive timeout windows that would melt at scale.

To view this discussion on the web visit https://groups.google.com/d/msgid/rapidpro-dev/4c266de4-d3a7-4488-b128-891f6bab7b5bn%40googlegroups.com.